Class / Field parsing error?? about idldoc HOT 5 CLOSED

Author: jhood
I did some testing to try and learn more about this. If I have a number of similar structure definitions in a file the 2nd and on procedures (name2!__define, etc.) are converted to class definitions and the @field lines are parsed without error, and show correctly in the IDLDoc output.

I noted that your source code tends to put the name!__define procedure near the end of the file. Maybe this is a clue to the difference?

Note as well that these filenames don't end in !__define though you seem to have removed this restriction from your parsing of structure/class definitions.

from idldoc.

There is some oddities with the class handling. The filename shouldn't have to end in __define, but I don't think I have any tests where it doesn't right now.

Normally, I only have one class per file and to make the classes found automatically, I put the __define routine as the last routine in a file with the same name. There are a few examples of multiple classes in a single file, though (MGffTemplate has a few helper classes in the same file that it is defined in).

from idldoc.

See r436 for some changes that might affect this ticket.

from idldoc.

Changeset r439 should fix this. I also added a test regression/nonautoclasses/ for this case.

from idldoc.

Author: anonymous
Most of my errors have gone away. I would also consider this issue closed. I will investigate remaining errors and repair my markup or open a new ticket if required.

from idldoc.