Joel de Guzman wrote: > I think it's a good suggestion, and no, I don't think it messes any > internals (at least none that I can think of); apart from the danger > of template name collision when we'll have more and more templates. > We do not have template scopes right now, but they will happen > eventually. Seems that you're implying putting these templates in > topmost (global) scope?
Yes, it would have to be in topmost scope. Actually it might be useful to have two templates for each section name: [link_section_name] link with title of section as text. [target_section_name] just the link target, use as: [link [target_section_name] Some other text] Assuming "section_name" is the name you gave to the section. Maybe there are better ways of mangling the template names though? > Related: I too find linking tedious. Right now, what I do is write > some macros at the topmost for the links and refer to them. At least > they are all in one place and I can change them relatively easier. > Examples: > Whenever I have additions or tweak this macros when the doc structure > changes, I hope for a better way. Yes, that's what I do as well, but it's still tedious and error prone. > So... Since it seems I'll be writing a preprocessor anyway (sometime > soon). I think it makes sense to have this feature. Hey, cool! BTW I spotted your message about literate programming, but haven't had a chance to try it in anger yet, like most things in life I could really have used this about 6 months ago :-) Cheers, John. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
