[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Orca/C is a bad compiler
- Subject: Re: Orca/C is a bad compiler
- From: wsquires@lonestar.utsa.edu (William H. Squires)
- Date: Tue, 8 Jun 1993 20:00:04 GMT
- Distribution: usa
- Followup-to: <???>
- Keywords: Byteworks,Orca,C,compiler
- Newsgroups: comp.sys.apple2
- Organization: University of Texas at San Antonio
- Sender: news@ringer.cs.utsa.edu
- Summary: Sort of. See text below
I'm glad this Orca thing got worked out. Personally, I prefer having the
twiddling cursor -- I know if the machine has flown south, if the cursor stops
spinning! :) I don't know about this init stuff, though.
To those still having trouble with Orca/C 2.0.?, remember, install your
Byteworks languages (2.x versions) from oldest to newest, using the Installer
in the newest version. An example: I have Orca/M,C,and Pascal 2.1 (2.0.1?).
I got Orca/M 2.0 first, then Orca/C 2.0, then Orca/Object Pascal just a few
weeks ago. Therefore, I Installed Orca/M, then Orca/C, and finally Orca/Pascal
all using the Installer on the Pascal Disk(s). Be sure to copy any useful
LOGIN, SYSTABS, =.INT, and =.H files before installation, then put them back
when you're done.
BTW, for those who must (or like) to use DOS (or Unix), I have a LOGIN file
for Orca/Shell that emulates most common MSDOS and Unix commands using the
ALIAS shell command, or custom utilities in the 0/ORCA/UTILITIES/ folder. If
you want the utilities (and/or the C source), email me. It might take a while,
though. I'll have to uncompress the source from GSHK archives, along with some
of the EXE files that aren't in the above mentioned folder.
Another handy tip. If you have Orca/C 1.x, compile and debug your programs
from there using the shell (or better yet, Orca/Debugger), then recompile
under Orca/C 2.0 (you should use ANSI function prototyping as much as possible
to avoid trouble with C 2.0). Also, make Orca/Shell (ORCA.SYS16) part of the
Quick Lanuch list under system 6.0, and QUIT if you get a linker error of any
sort. Re-lanching the shell takes care of the problem that will result if you
keep going after a linker error. You should also do this if you get lots of
syntax errors in C or Pascal. Orca/M doesn't seem to have this problem.
BTW: coming soon to an x86 machine near you (//GS lovers will love this
QuickTime movie) -- Jurassic Park(ing): DOSasaurus LeX kills it's own user's
hard drive. User retaliates by buying a //GS! :) (Seriously folks, this is
just a play on words, there isn't actually a QuickTime movie by this title!)
wsquires@lonestar.utsa.edu