Re: Implementing C/C++ style #include...

["Marin David Condic" <marin.condic.auntie.spam@pacemicro.com>]

That is yet another technique for building in debug code - again suitable
for a variety of things, but not necessarily a complete answer. (Can't
appear in a declarative part and is really a technique for logging output -
not a general means of encapsulating general code you'd like to use or not
use depending on configuration.)

One issue is the potential procedure call overhead - not a concern in most
apps, but in some. Possibly with judicious use of "pragma Inline" the
compiler may optimize it away. It also may create verification issues if
your project has some really tight testing constraints.

A bit of a narrower technique for getting some debug code into a program &
one I've used in a few situations. It is especially useful if you'd like to
keep the debug code in the production app and be able to toggle it on/off at
runtime.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"singlespeeder" <singlespeeder@32sixteen.com> wrote in message
news:99dpom$169$1@neptunium.btinternet.com...
> I use a Trace package with two bodies, one which contains null stubs. Then
> use the make script to select the right body to load into the Ada library
> before compiling. Calls to the trace package don't have to be wrapped in
> if-then-else's
>
> with Trace;
> ...
> Trace.Log_Line ("some text to log to file")
> ...
>
> Nick
>
>