[Scons-dev] probe interface for run-time introspection of SCons internals

[anatoly techtonik]

Here is the "probe" concept for getting details out of SCons:
https://bitbucket.org/techtonik/scons/commits/branch/probe
or more specific:
https://bitbucket.org/techtonik/scons/commits/c98336b6f7ea24ae111a2f959688e6a458266887?at=probe

Basically, in your launcher script you define a function to
process signals from SCons core. This may migrate into
command line API, but then command line processing will
be missing. That's why this is a low level interface.

The advantage is that if probe is a null function, it might be
possible for implementation like PyPy to skip the call, so
no performance overhead on top of allocating memory for
debug strings.


If you have a real world scenario that you use (or plan to
use) and this approach creates problems and is not
extensible for them, I am interested to know about it.
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20140531/697d0a32/attachment.html>