SCOUG-Programming Mailing List Archives

>> Next Message >>

Date:	Sat, 14 Feb 2004 07:36:22 PST8
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com
Subject:	SCOUG-Programming: PL/I most important statement (was: call(TZ) ? - PL/I)

Content Type: text/plain

Lynn H. Maxson wrote:
>
> Only variables with the automatic, controlled,
> or based storage attributes get deallocated on
> exiting the begin-block. That says variables
> with the static storage attribute do not.

Yes. That's why I use static variables to maintain values which I will
need later.

And I can INIT a static variable and it won't INIT again (my guess is
the INIT value is loaded with the executable rather than placed there
with setup code).

> I thank Bob for reinforcing my earlier response.

And Bob also reinforced mine:

Bob said:
> The difference is who has to remember what has been
> allocated. In C you have to do it (some types of
> allocation are freed when you exit a procedure but
> not all). In PLI the compiler does it.

I prefer to let the compiler do it. Why create work for yourself?
Lynn, wasn't your Warpicity project laced with the concept of "let the
compiler do it"?

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 14 | February | 2004 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.