SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 13 | February | 2004 ]

<< Previous Message << >> Next Message >>


Date: Fri, 13 Feb 2004 20:18:35 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

> Peter Skye
>
> > Throw that allocate in the trash can, Lynn. Use BEGIN.

Bob wrote:
>
> In PL/I when you exit a procedure all memory allocated
> in the procedure is freed when the procedure exits.

Hi Bob, thanks. That's a good succinct summary.

I like my BEGIN blocks because they represent "logical groupings" of my
logic. I could shift one way and replace them with PROCs, or I could
shift the other way and place the BEGIN block code inline with the code
that contains it (and remove the BEGIN).

Of these three options, I chose BEGIN. When I leave the BEGIN block
everything is wrapped up automatically and I have a "fresh start" for
the following section of code without having to check backwards to see
what was allocated and must be deallocated. And as for PROCs, they have
a bit more overhead and, frankly, I think they're unsightly when they
appear in the middle of other code (I like to keep stuff straight-line
so I can easily understand it later).

- 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".

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


<< Previous Message << >> Next Message >>

Return to [ 13 | February | 2004 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.