SCOUG-HELP Mailing List Archives
Return to [ 05 | 
August | 
2002 ]
<< Previous Message << 
 >> Next Message >>
 
 
 
Content Type:   text/plain 
=====================================================  
If you are responding to someone asking for help who  
may not be a member of this list, be sure to use the  
REPLY TO ALL feature of your email program.  
=====================================================  
 
J.R.,  
 
>The 2 versions are not 100% compatible, but nearly so.  
 
What I meant to say here is that OREXX is not 100% fully backwards  
compatible with CREXX, but almost!  
HCM  
______________________________________________________________________________  
 
Harry Chris Motin wrote:  
>   
> =====================================================  
> If you are responding to someone asking for help who  
> may not be a member of this list, be sure to use the  
> REPLY TO ALL feature of your email program.  
> =====================================================  
>   
> J.R.,  
>   
> Both Object and Classical REXX come FREE with Warp (I don't remember  
> which version, either 3 or 4). The 2 versions are not 100% compatible,  
> but nearly so. There are some things fixed in Object REXX and there are  
> a few things that work differently (read that as "better") in Object  
> REXX.  
>   
> When you first try to run a program under OREXX, the REXX interpreter  
> scans it first and determines whether or not there are any coding  
> errors. If so, it refuses to run and instead tells you about the errors.  
> In CREXX a program runs until it reaches the error, then stops.  
>   
> Also, I believe that there are 1 or 2 instances of incorrect, or  
> improper, coding that you could get away with using CREXX, but not  
> OREXX. Therefore, if you made any of these coding errors your program  
> will run under CREXX but not under OREXX. You have to fix the errors to  
> have it run in Object.  
>   
> On my system I use VisProREXX. When I save a VisPro project/program as  
> an *.exe executable, and also I am using Object REXX, then it will  
> refuse to run, if I switch to CREXX (or vise versa). I have to resave  
> the VisProREXX executable under CREXX after I have switched to CREXX.  
>   
> Bet this is more than you wanted to know. Right?  
>   
> HCM  
>   
> ______________________________________________________________________________  
>   
> "J. R. Fox" wrote:  
> >  
> > =====================================================  
> > If you are responding to someone asking for help who  
> > may not be a member of this list, be sure to use the  
> > REPLY TO ALL feature of your email program.  
> > =====================================================  
> >  
> > HCM wrote:  
> >  
> > > The best and easiest fix would be for you to switch your system to  
> > > Object REXX. Do so by going to a commandline and switching to the "OS2"  
> > > directory where your OS is installed (like "C:\OS2"). Then type  
> > > "SWITCHRX.CMD" at the commandline. Then reboot.  
> > >  
> > > Object REXX is better. There are more functions and enhanced functions.  
> > > Upon rebooting the system replaces the help file for Classical REXX with  
> > > the corresponding help file for Object REXX. You probably won't notice  
> > > any difference between Classical and Object REXX, except greater  
> > > functionality.  
> > >  
> > > If you do not want to switch  
> >  
> > >From what you say, and based on the inference that Object is going to be backwards compatible for routines written in Classical -- but NOT vice-versa -- is  
> > there any possible reason *against* making this changeover ?  I was not aware that this stuff was all (apparently) included, previously being under the  
> > impression that one had to go out and purchase Object REXX separately.  If it's already there, or free for download somewhere, that would make it easy.  
> >  
> > Jordan  
> >  
> > =====================================================  
> >  
> > To unsubscribe from this list, send an email message  
> > to "steward@scoug.com". In the body of the message,  
> > put the command "unsubscribe scoug-help".  
> >  
> > For problems, contact the list owner at  
> > "rollin@scoug.com".  
> >  
> > =====================================================  
>   
> =====================================================  
>   
> To unsubscribe from this list, send an email message  
> to "steward@scoug.com". In the body of the message,  
> put the command "unsubscribe scoug-help".  
>   
> For problems, contact the list owner at  
> "rollin@scoug.com".  
>   
> =====================================================  
 
=====================================================  
 
To unsubscribe from this list, send an email message  
to "steward@scoug.com". In the body of the message,  
put the command "unsubscribe scoug-help".  
 
For problems, contact the list owner at  
"rollin@scoug.com".  
 
=====================================================  
 
  
<< Previous Message << 
 >> Next Message >>
Return to [ 05 | 
August | 
2002 ] 
  
  
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.
 
 |