Here's what I'm dreaming of for PasDoc2:
- wiki formatting for source code comments (must be modified because indentation cannot play a role)
I put some comments about wiki syntax on my personal page, see Michalis' comments about wiki-like syntax. – MichalisKamburelis
- new parser (using Martin Waldenburg's excellent Lexer)
- plugins for tags instead of hard-coding them
This is not so far away to implement now, that we have TagManager. Adding new tags to pasdoc code is trivial now, basically you just do
1 TagManager.AddHandler('...', {$IFDEF FPC}@{$ENDIF} TagHandlerProc, [...], [...]);and implement TagHandlerProc. So it seems that allowing user to specify via command-line some so/dll/dylib with a hook like RegisterTagHandlers that is called from TDocGenerator.ExpandDescription is not a big deal. If anyone has a usable idea for using such plugin-system, please speak up on MailingList, and we can see into this – MichalisKamburelis.
- parse units in dependency order, ie. when a unit is encountered that uses another unit, then try parsing that other unit first. If it cannot be found, then write a warning. Allow giving a list of units that should not be warned about, and ship a default RTL list.
- proper caching of an intermediate format, not the final generated documentation
(Done) I just treated TPasItem tree (with RawDescription values attached) as the proper "intermediate format" for cache. No need to invent anything new here. – MichalisKamburelis.
- more ideas here...