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).
My idea was that one would use stdin as the script to be run by some command, because there was some concern about keeping this stuff separate from the docs.
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?
Wave's scheme keeps things simple and straightforward. Exactly because of that feature I think it is superior.
I initially thought one might want to put error messages in the docs, but this could also be accomplished in the script so I'll go with the KISS principle.
Jo�o
------------------------------------------------------- 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_id=6595&alloc_id=14396&op=click _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
