Comment 10 for bug 1358392

Thanks for posting the in-line change version, that's very helpful. I haven't digested the full set of changes yet, but just as a heads-up, the use of specific fields (well, the prefix thereof) won't work for the final version, but that's fine for now to get the point across. Reason being, there is nothing saying that the 4XX fields will be the location of unauthorized headings in any given control set, that just happens to be the case for the LoC one.

I'll look at the net effect and see if I can suggest a solution that fits with the rest of the code. Just as a warning, I'll be out of the office and away from all computers tomorrow through next Tuesday, though, so it will be a few days until I can do that, though.

I also want to say that I'm very glad that you are looking at the guts of this code, as often it's hard to spread the knowledge of the more complex internal workings in many areas and jumping in really is the best way to learn it well. Thanks for digging into it!