John Maddock wrote:
> Allan Clark wrote:
>> Sorry all... I didn't mean that as a broadcast.
>>
>> (and the link would be a Literate-Programming link, if I could spell)
>>
>> Allan "oops" Clark
> 
> LOL :-)
> 
> See http://article.gmane.org/gmane.comp.lib.boost.documentation/2264
> 
> Possibly calling it literate programming is an exageration: it's more like a 
> code extraction tool, but it's heading in an interesting direction I think.

I call it reverse-Literate-Programming. In true Lit-Programming, the
docs drive the code (e.g. weaves the snippets into actual cpp files).
This reverse-lit is useful in cases where you already have code
written that you want to document in Qbk.

Anyway, we're definitely heading towards that (full Lit-Programming).

> You certainly could write all your code and docs in one file if you wished, 
> but perhaps of more interest would be "anotated" examples that get pulled 
> into the docs.  alternatively marked up source or headers for documenting 
> the internals / implementation method.  Would make a nice way of creating 
> articles / presentation material methinks :-)

The quickbook-markups-in-comments is a nice idea. I credit Rene Rivera
for that nice idea.

Regards,
-- 
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net


-------------------------------------------------------------------------
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

Reply via email to