Defects Corrected

• The C++ scanner had a longstanding problem with code like this: class A { void A::foo(); }; (Note the unnecessary qualification.) It also goobered up cases where the qualification was something other than the original class name, for instance, if you were implementing two interfaces that have methods with the same name.
• The C++ Compiler didn't deal with an external dereference operator; e.g. yow &operator *( const yowPtr & );
• The HTMLHelp Compiler is a surprisingly elusive critter. Its install script doesn't seem to behave consistently, which means that sometimes DocJet is unable to find the thing. In the past, the only work-around was to dork with the registry. The fix was to have DocJet search in the path for the HTMLHelp compiler. Thus we just provide a sensible and hopefully more predictable fallback.
• The VB.Net scanner was throwing an exception on all projects it was asked to scan.
• The C++ scanner setting "Get comments from headers" didn't work as advertised.
• The XML comment transformer advertises that you can make transforms that use attriubtes of the call with "$yow$" rather than "$$", which is the body. That didn't work.
• The External Sources Specification could get botched up if you used Drag&Drop to create copies of objects from the code. (Which isn't a good thing to do.) The editor has been fixed so it won't allow you to create the copies.
• DocJet's generated HTMLHelp documentation had folders as the icons for expandable entries in the table of contents. Most folks seem to prefer books over the folders, so the HTMLHelp output type has been changed to do that.
• The C# scanner could get into an infinite loop if you used the "unsafe" keyword.
• If you had a declaration with a line in it long enough to be wider than the average browser window, then, in most versions of IE, the blue margin bar was jammed together with the text of the page.
• The Comment Transformer (the executable that will take code written with one style of comments and convert it to the DocJet style) would go into an infinite loop if the last line of a file was a "//" comment.
• The C# scanner wasn't correctly sorting out the ownership of parameters, which could cause botched output on overloaded functions.
• The $(ForeachOverload) function was not finding all the parameters of overloaded functions, causing some errors in the display of multi-lingual (.Net) output.
• The Table Scanner could crash if given a table-begin markup with nothing after it (in the same comment section).
• The JavaDoc and XML comment scanners would not do the right thing if the comment for an argument was not on the same line as the @PARAM markup.
• The Table Scanner could fail to generate correct output if a titled-table had no blank line (or dashed lines) between the title-row and the body.
• If you tried to edit the settings for RegExp Hook on a machine that had never had Visual Studio 6 installed on it, you would get an error message and the settings dialog would not work.
• If you installed DocJet on a machine that has VS.Net 2003, but never had VS.Net 2002, the VS plug-in would fail because a couple of DLL's were missing.
• If you don't use Argument Hook and you have undocumented-parameters warnings turned on, you'll get warnings even if you have a "parameters" argument section.
• The VB IDE plug-in did not work for users without permission to modify HKEY_LOCAL_MACHINE.