> A new update in
code documentation syntax. I think this have evolved much
> since the
first version. But need more discution until reach a solid stage.
> Maybe
it is time of balancing the costs against the benefits.
> Please take a
look at the specification and send your comments, preferences
> and
questions. This is a not so prioritary project, but it could bring good
>
advantages for the language by having a start in this direction.
>
> Saudações
>
> Juarez Rudsatz
Looking great. This docGen thing will add
value to D.
My suggestion,
Parhaps there could be a way to modularise the
docGen, so that files that don't change don't need to be re-worked with doc gen.
That may not need to be in the documentation though. Also it would be nice if
users could specify a webpage where the latest docgen document
resides. That way local versions could remain current.
ie
/*
*/
Parhaps this could be done with see, however I
think it could be neetly formated into the headers(or footer) of the
page.
The above may produce something like (for the
car page):
Of course theres the possiblily of bad links, like
when the webpage\class structure changes. In these cases a default docgen
page could also be created to capture these errors.
It would be nice if the docgen produced pages into
separt folders depending on the package which they reside, optionally or a zip
file. That's more a docgen compiler thing then a spec thing.
Joel Anderson
PS -
copyrigth ?? -> copyright