Why is TRACE an EXECUTABLE Statement at all?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Why is TRACE an EXECUTABLE Statement at all?

ThSITC
Hello there,

    1.) I don't know whether I should discuss this topic here *or* in
[hidden email]. Please advise! :-)
    2.) The issue is as follows:

When, after a leading TRACE ALL, after a METHOD Directive (clause), and
a couple of ordinary
statements (clauses), including a couple of valid RETURN's, a TRACE OFF
is encountered,
then the current NetRexx Compiler complains:

Clause cannot be reached

if all branches in a conditional statement already do contain the proper
RETURN statement (Clause)

I personally do think, TRACE should be regarded and handled as a
Directive (as I call them)
*and NOT* as an ordinary clause :-)

Kind regards from dark Vienna,
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/

Thomas Schneider, Vienna, Austria (Europe) :-)

www.thsitc.com
www.db-123.com
Reply | Threaded
Open this post in threaded view
|

Re: Why is TRACE an EXECUTABLE Statement at all?

Patric Bechtel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

it's not a directive, although it feels a lot like one. But the fact
that it isn't makes the following possible:

if debug then
   trace results
else
   trace off

I love this feature, and I bet there's more of us out there.

It's fine the way it is.

cu,

Patric

Thomas Schneider schrieb am 30.01.2012 19:14:

> Hello there,
>
> 1.) I don't know whether I should discuss this topic here *or* in
> [hidden email]. Please advise! :-) 2.) The issue is as
> follows:
>
> When, after a leading TRACE ALL, after a METHOD Directive (clause),
> and a couple of ordinary statements (clauses), including a couple
> of valid RETURN's, a TRACE OFF is encountered, then the current
> NetRexx Compiler complains:
>
> Clause cannot be reached
>
> if all branches in a conditional statement already do contain the
> proper RETURN statement (Clause)
>
> I personally do think, TRACE should be regarded and handled as a
> Directive (as I call them) *and NOT* as an ordinary clause :-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: GnuPT 2.5.2

iEYEARECAAYFAk8oIl0ACgkQfGgGu8y7ypBPBQCg7pfuRZBAVJYBoFZIcxkwnmJb
OjoAmgOxfMLvDuhO7U+Io36ovG/5aD3x
=LjbW
-----END PGP SIGNATURE-----

_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/