On Monday 10 November 2003 08:57 pm, Eric Friedman wrote:
> Eric Friedman wrote:
> > Doug (or others)-
> >
> > Right now it seems the <description> element has no effect on the
> > generated HTML when inside a <typedef> tag nested in a <class>. For
> > instance, I have documented the variant<...>::types typedef, but this is
> > not visible in the generated HTML.
> >
> > I really don't want to have to use a <purpose> element, since the
> > resultant formatting is amenable only to short blurbs IMO.
> >
> > Thanks,
> > Eric
> >
> > P.S. On a related note, it would also be useful to be able to document
> > typedefs that are not nested in a class. I don't know if this is easier
> > or harder to implement than the nested typedef case, but in any case I
> > don't need it now. Just thinking into the future :)
>
> While I'm at... <g>
>
> It would also be useful at some point to have <typedefname> to link.
>
> Eric
I'm quite busy now, and am not going to get to this for a while. Maybe there's
a brave soul around that wants to learn some XSL? <crosses fingers>
Doug
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
