TRACING *Local* Variables *versus* public or shared *properties*

[ThSITC]

For some, not yet known to me, reasons,

the currently available TRACE VAR

in NetRexxC does *NOT* (repeat NOT) trace PROPERTIES, nor is it allowed,
nor implemented,
to denote a shared or public property in the *NetRexx* TRACE VAR
instruction.

I did not yet fully decypher why this is so, as it is (by reading the
NetRexxC Source Code).

The purpose of this mail is *to collect knowledge*, whether it would not
be very wise to
be able to REFERENCE public/shared PROPERTIES in the TRACE VAR
statement, as well.

Also, I (personally) would think that the DIRECTIVE TRACE (with any/all
options) shall be allowed
ANYWHERE in a NetRexx program. TRACE, as it is, is NO EXECUTABLE
statement (Verb).

It shall be regarded as SWITCHING some environment variables, such that
the proper
trace Code is emitted by the Compiler.... :-)

What do you think?

Thomas Schneider.


--
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/