Hello all,
I think I am meanwhile very well known in this community to raise
*unwanted* and *unneeded* discussions.
Nevertheless, I'm trying it again!
Currently, the TRACE statement becomes effective when executed.
e.g. TRACE ALL sets (internally) the TRACE Generation flag.
... and does then generate TRACE Code.
As far, as excellent.
However, after many tries, and pitfalls as well, I *personally* do
*think* that the
effect of a TRACE statement (I do call TRACE a directive, NOT a Verb, by
the way)
SHALL be SCOPED!
e.g. when I do have a sourc code of
method GetExpression() public returns int
TRACE all
... then:
The TRACE should TERMINATE after the return of this method.
The current implementation in NetRexxC traces everything after the
TRACE in the example code, i.e. the intenal NetRexxC compiler flags
are set in a way, that they do remain effective aftr isuing the TRACE.
This shall and should be changed in the next release of NetRexxC, IMHO!
Sleep well, al together!
Crazy Uncle Thomas (Massa Thomas, as my Egyptian friends here in Venna
do call me :-)).
=======================================================================
--
Thomas Schneider (Founder of www.thsitc.com) Member of the Rexx Languge
Asscociation (www.rexxla.org) Member of the NetRexx Developer's Team
(www.netrexx.org)
_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive :
http://ibm-netrexx.215625.n3.nabble.com/
Thomas Schneider, Vienna, Austria (Europe) :-)
www.thsitc.com
www.db-123.com