Just catching up with the state of affairs...

...

Really the implementors ought to be using something like HeaderDoc or whatever and write these descriptions as they code... just a thought...

Again I agree with you. I have only been able to find pasdoc but it was wrote for delphi/kylix/fpc which means the code may not be portable to gpc. It also has not been touched in a couple of years. I grabed a copy of the source and am going to take a look at getting it ported to gpc and add some things to it. For instance right now it will output HTML and Texi. The HTML part is OK but I will need to work on the Texi part and change it to texinfo as that is what is being used for gpc. I may actualy just end up rewriting it from scratch as it is using quite a few custom class that duplicate units gpc already has and I would prefer to use the ones gpc provides verses costom ones.

I'm trying to implement my own little scheme, but written in C (don't look at me!). I get the feeling mine wind up a little more basic, but it'll be mine, all mine! :-)

Grant