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 10:04:29 PST8
From: "Lynn H. Maxson" <lmaxson@pacbell.net >
Reply-To: scoug-programming@scoug.com
To: < "scoug-programming@scoug.com" > scoug-programming@scoug.com >
Subject: SCOUG-Programming: call(TZ) ? - PL/I

Content Type: text/plain

Peter,

I've done contract software using PL/I and the OS/2 APIs. In
one instance we were involved in writing a centralized
database administration system with remote support for all
the major operating systems at the time, including Windows,
OS/2, Novell, and UNIX. We had the OS/2 portion. I gained
considerable experience with the C interface used by OS/2.

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.

Today except for "ON" conditions the "BEGIN" statement does
not occur. I would probably favor the "END" statement as it is
the common terminator for the "PROC", "BEGIN", "SELECT",
and "DO" statements. However, I feel the most important is
probably the assignment statement in its support of aggregate
operands as well as allowing mixed operators (string,
arithmetic, and boolean) within an expression. I don't want to
slight the PL/I builtin functions either. Or maybe even the
"SIGNAL" statement which supports programmer- as well as
system-defined interrupts, i.e. exception conditions. Nah,
there are too many important ones which somehow K&R in
defining C regarded as "unnecessary" and the C++ along with
the JAVA people have had to introduce. Someday maybe
they will catch up. It's only taken them 30 years to get this
far.

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

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.