Comments (5)
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.
Related Issues (20)
- Subversion keywords are interpreted as equations
- Update to MathJax v2.0 HOT 2
- Ability to show only commands in code snippets HOT 1
- Inherited properties HOT 1
- Use sphinx to generate documentation
- Directives for specific output types
- Problem parsing BEGIN with an extra $ after it HOT 1
- Images not referenced correctly in LaTeX output HOT 1
- Display of links in LaTeX output
- Properties and fields should be in alphabetical order HOT 1
- Make install target
- Fields don't show default value HOT 2
- Make "Get" and "Set" an IDLdoc keyword like "GetProperty" and "SetProperty"
- Shows ancestor class methods HOT 1
- Filter errors/warnings in output
- Update available
- rst code markup should link to online docs HOT 1
- Multiple arguments per line
- COMMENT_STYLE keyword only changes the extension of the output HOT 5
- undefined procedure: 'MGCOARRAYLIST__DEFINE' when running first tutorial example HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from idldoc.