Douglas Gregor wrote: > On Thursday 06 May 2004 01:46 am, Vladimir Prus wrote: > > Well, I use doxygen, so I have no control over what's produced ;-) > > Actually, you have some control :) Grouping of overloads is done with the > "\overload" tag, like so: > > /** > * What wonderful documentation this is. > */ > void foo(int); > > /** > * \overload > */ > void foo(double); > > This way, BoostBook will just "do the right thing" of grouping the > \overloads together using the documentation from the first. Doxygen's > output is a little less pretty, but that's my opinion :)
The problem with this is that you can't add specific documentation for each overload. E.g: /** * \overload * If the parameter if INF, your monitor will blow up and your mouse will * bite you. */ void foo(double); The best solution would be to automatically group all overloads on the same HTML page. > > BTW, isn't it possible, after emitting "Reference to ... is ambiguous" > > message to just generate the link to the first found node? > > It's possible; I'm just not sure how hard it is :) and later: > Not very. It's done now. Thanks. At least I don't get broken links now ;-) - Volodya ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
