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 [ 03 | August | 2001 ]

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


Date: Fri, 3 Aug 2001 10:17:43 PDT
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Boot drive ?

In <3B6A55A3.2987@peterskye.com>, on 08/03/01
at 12:41 AM, Peter Skye said:

>Mr. Quackles says you did it on _purpose_ just to harass me. _____

Nah, it was just a testcase to see if you were paying attention and
thinking about what you were reading. :-) You use Classic REXX. The
discussion indicated that the documentation was in the Object REXX manual.
Naming an Object REXX manual CREXX.INF might make sense to some folks just
not me.

BTW, did I ever tell you I'm a lousy proofreader?

>Now then, I want my Classic Rexx programs to use the Object Rexx function
>calls (such as "SysBootDrive()"):

Well, since the function is defined in Classic REXX's REXX.DLL, is it
really an Object REXX function? I'd say not. It's just that IBM chose
not to update the Classic REXX manual.

>-- 2. When I do a SysLoadFuncs() should I use "OREXUTIL.DLL" instead of
>"REXXUTIL.DLL"? I currently do this:

No.

> rc = rxFuncAdd( "SysLoadFuncs", "RexxUtil", "SysLoadFuncs" )
> ...
> rc = SysLoadFuncs()

This is fine. Do a testcase to prove it to yourself. Since RexxUtil is
almost never unloaded use rexxtry:

say sysbootdrive()

>I *presume* I'm supposed to use "ORexUtil" instead of "RexxUtil" when I
>call rxFuncAdd() because the DLLs are named REXXUTIL.DLL and
>OREXUTIL.DLL. Yes?

If you do, you will probably crash something.

>-- 3. Since ORexUtil.dll is smaller than RexxUtil.dll, I'm wondering --
>am I supposed to rxFuncAdd() them *both*? Is there any reason I should
>continue to use RexxUtil? Is there any functionality in RexxUtil that
>isn't in ORexx? Does ORexUtil.dll load RexxUtil.dll by itself without me
>explicity doing so?

No, no and no. the Classic RexxUtil implements a subset of the functions
implemented by the Object REXX version. The Object REXX version
implements functions that require functionality not available in Classic
REXX's REXX.DLL.

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.28a #10183 Warp4/FP11
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------

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

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 [ 03 | August | 2001 ]



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.