You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At some places such as in aseba/compiler/compiler.cpp for method compile, the doxygen documentation of public methods is located in the cpp file. It would be better to put it in the header file (aseba/compiler/compiler.h), because the cpp file could be provided as compiled code and not readily available. That's already the case for some of the public declarations (e.g. struct SubroutineDescriptor).
The text was updated successfully, but these errors were encountered:
For information, this was a design choice: at the time the compiler was written, code folding wasn't very widely available in editors and so the idea was that either someone knows more or less the code and wants to get a quick look at the available functions, and thus reads the h file, or this person wants the detailed information, and reads the generated documentation. This rationale might still be valid for people using editors such as vim.
At some places such as in aseba/compiler/compiler.cpp for method
compile
, the doxygen documentation of public methods is located in the cpp file. It would be better to put it in the header file (aseba/compiler/compiler.h), because the cpp file could be provided as compiled code and not readily available. That's already the case for some of the public declarations (e.g.struct SubroutineDescriptor
).The text was updated successfully, but these errors were encountered: