lphillips@lpami.wimsey.bc.ca (Larry Phillips) (09/16/90)
In <2516@dsacg3.dsac.dla.mil>, nfs1675@dsacg3.dsac.dla.mil ( Michael S Figg) writes: >I've been working with the 'CygCC' AREXX tutorial in the latest Amazing >Computer, and although the tutorial is excellent, I'm having trouble >getting it to run. This program is a driver to glue CED and that Lattice >compiler. It contains 4 AREXX scripts which occasionally call each other. >I've stored the 4 in the REXX: directory with the proper '.rexx' suffix >but CED doesn't seem to be able to find them. The main driver 'CygCC' will >run from the CED 'send DOS/AREXX command' but only if I give it a fully >qualified pathname like 'REXX:CygCC.rexx'. It then ends when trying to >call another one of the scripts ('FindWind') with an AREXX return code of >10. CED is running under WShell, and things look okay if I try them from >the shell instead. They don't go very far when called from the shell, but >then they where designed to not go very far if not called from CED. I can >call the programs with just the name under the shell and it is found as >normal in the REXX: directory. Yes, the REXX: directory is assigned and I've >run 'rexxmast'. I'm using current version of AREXX and CED, plus Lattice >v5.05. > >To me it seems to be a problem with CED (not CED's problem, probably mine) >and how it searches for functions, etc. Try changing the suffix on the files from '.rexx' to '.ced'. -larry -- It is not possible to both understand and appreciate Intel CPUs. -D.Wolfskill +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+
nfs1675@dsacg3.dsac.dla.mil ( Michael S Figg) (09/16/90)
I've been working with the 'CygCC' AREXX tutorial in the latest Amazing
Computer, and although the tutorial is excellent, I'm having trouble
getting it to run. This program is a driver to glue CED and that Lattice
compiler. It contains 4 AREXX scripts which occasionally call each other.
I've stored the 4 in the REXX: directory with the proper '.rexx' suffix
but CED doesn't seem to be able to find them. The main driver 'CygCC' will
run from the CED 'send DOS/AREXX command' but only if I give it a fully
qualified pathname like 'REXX:CygCC.rexx'. It then ends when trying to
call another one of the scripts ('FindWind') with an AREXX return code of
10. CED is running under WShell, and things look okay if I try them from
the shell instead. They don't go very far when called from the shell, but
then they where designed to not go very far if not called from CED. I can
call the programs with just the name under the shell and it is found as
normal in the REXX: directory. Yes, the REXX: directory is assigned and I've
run 'rexxmast'. I'm using current version of AREXX and CED, plus Lattice
v5.05.
To me it seems to be a problem with CED (not CED's problem, probably mine)
and how it searches for functions, etc.
Thanks for any help.
---Mike,
--
A man said to the Universe "Sir, I exist!" | Michael Figg DSAC-FSD
"However," replied the Universe, | DLA Systems Automation Center
"The fact has not created in me a | Columbus, Ohio
sense of obligation."- Stephen Crane | mfigg@dsac.dla.mil CIS: 73777,360jdege@ (Jeff Dege) (09/18/90)
In article <2516@dsacg3.dsac.dla.mil> nfs1675@dsacg3.dsac.dla.mil ( Michael S Figg) writes: > > >I've been working with the 'CygCC' AREXX tutorial in the latest Amazing >Computer, and although the tutorial is excellent, I'm having trouble >getting it to run. This program is a driver to glue CED and that Lattice > >To me it seems to be a problem with CED (not CED's problem, probably mine) >and how it searches for functions, etc. > >Thanks for any help. > > Most ARexx hosts look for application-specific extensions. In this case, CygnusEd looks for rexx:cygcc.ced. One other thing you might need to watch for. If you are using Wshell, and are running teh setexecute patch, you'll need to add a "sygnal off error" line to cygcc, otherwise it will abort if LC returns an error code.
duncant@mbunix.mitre.org (Thomson) (09/20/90)
In some previous article someone writes: >> >>I've been working with the 'CygCC' AREXX tutorial in the latest Amazing >>Computer, and although the tutorial is excellent, I'm having trouble >>getting it to run. >> Hi, I'm the guy who wrote CygCC and the AC article. I haven't encountered the problem you describe on my system... What version of ARexx are you running? Do the file names have ".ced" on the end? BTW, did you get the thing on disk or did you type it in from the listings? AC sent me some copies of the magazine, but they didn't send me the disk version, so I don't know how they organized it on disk, or what file names they gave things, etc. I'll poke around on my own system and see if I can duplicate your problem. BTW BE SURE TO SEE THE CYGCC BUG FIX POSTING ON COMP.SYS.AMIGA Duncan Thomson Newsgroups: comp.sys.amiga,comp.sys.amiga.tech Subject: Re: A3000 and WB2.0 --- HELP!!! Summary: Expires: References: <1788@nemesis.stsci.edu> <1990Sep18.190542.25968@agora.uucp> <1990Sep19.000307.4728@uokmax.uucp> Sender: Followup-To: Distribution: Organization: The MITRE Corp., Bedford, MA Keywords: a3000,wb2.0,ram,memory,bru -- (Please excuse the typos and garbage caused by line noise.)