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 11:34:58 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:
>
> > [the most important PL/I statement - Peter suggested BEGIN]
>
> The BEGIN statement in PL/I has two functions.
> - One, to mark the beginning of an "ON" code subroutine,
> for which purpose they could have easily used the "PROC"
> statement.
> - The second function allows a redeclaration of a variable
> within a code segment to differentiate it from an
> identically named variable in the same procedure but
> outside the code segment. That would allow two or more
> programmers to independently write segments of a program
> without concern for the variable names used.

Okay, good. I thought BEGIN also did memory allocation for whatever was
needed within its block. Yes? No?

> I feel the most important [statement] is probably the
> assignment statement in its support of aggregate operands
> as well as allowing mixed operators (string, arithmetic,
> and boolean) within an expression.

That was my second choice, right after BEGIN. You can't get much work
done without an assignment statement.

I *think* you're including expressions when you say assignment
statement, yes? Expressions can appear in a lot of places, of course,
but we usually think of them as being primarily a part of assignment
statements. First you evaluate the expression, then you "assign" the
result to the target variable.

> I don't want to slight the PL/I builtin functions either.

This choice is perplexing. Syntactically they just look like subroutine
calls, and code-generation-wise they're simply inlined. What's so
special about them?

> Or maybe even the "SIGNAL" statement which supports
> programmer- as well as system-defined interrupts, i.e.
> exception conditions.

Do you think PL/I's exception implementation is stronger than what is in
other popular languages?

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