Jo�o Abecasis wrote: > Well, here's a very rudimentary and not very thought out > proposal that may get us started on the processing of > doc-related-code... > > [process command args] > > ... content ... > > [endprocess] > > The 'process' directive shall execute 'command' passing it > the specified 'args' as command line arguments. The content > of the process directive will be used as standard input for > the command. > > 'command' shall be a platform and toolset independent command > (I'm imagining some promiscuity between bjam and quickbook > here... perhaps quickbook can invoke bjam for these steps). > > 'args' may include names of external files (this includes > collector's with a file name) and names of collectors. > > Both stdout and stderr of the invoked command may be made > available for inclusion in the docs in an as yet unspecified > manner (proposals > welcome!) or may be output to quickbook's stdout/stderr also > in an as yet unspecified manner. > > There might also be interest in redirecting stdout/stderr > through another processing step.
I have a very similar thingy in Wave, where you can specify a special #pragma wave system(some command) invoking the given command (no stdin redirection here, this is different). The stdout and stderr are intercepted. The stdout is used as the replacement text for the whole #pragma command and the stderr is used for error reporting purposes. Perhaps we could use it in the same way here: stdout is used as a replacement text for the whole [process section] and stderr is used for error reporting? Rgerads Hartmut ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
