Path: utzoo!attcan!uunet!world!decwrl!sdd.hp.com!zaphod.mps.ohio-state.edu!uwm.edu!rutgers!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!jh4o+ From: jh4o+@andrew.cmu.edu (Jeffrey T. Hutzelman) Newsgroups: comp.sys.apple2 Subject: Re: a2fx/hfslink Message-ID: Date: 6 Oct 90 19:09:43 GMT References: <9010051457.AA18841@apple.com> , <1990Oct6.051920.4341@utstat.uucp> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 30 In-Reply-To: <1990Oct6.051920.4341@utstat.uucp> Regarding ORCA/C. As far as I can tell after having used it for over a year, it is very close to ANSI compliant, but not perfect. For instance, it does not support the use of %p in format strings to print pointers. It expects a Pascal-type string for %p, which is far more useful on the platform on which it is running. It also allows \p as the first character of a string literal, which means store it with a leading length byte, like Pascal (but also with trailing null, not counted). This is because many of the toolbox routines require and/or return Pascal strings. I am currently in the process of porting a vi clone to the IIgs which was already written to be compiled on an Atari ST, UNIX, and other systems. I have had very little trouble; I'm only having a few problems now with a memory allocation bug in the program somewhere. The ORCA text-based shell is excellent; I have mine customized to look much like UNIX. It allows the easy addition of new utilities and commands. I do have problems with the desktop version; it's a great environment but I don't have enough memory for it to run well under system 5.0 or greater. Might be better under 4.0; I haven't tried. Overall, it's a prety good compiler and probably the best available for the IIgs. ----------------- Jeffrey Hutzelman America Online: JeffreyH11 Internet/BITNET:jh4o+@andrew.cmu.edu, jhutz@drycas.club.cc.cmu.edu >> Apple // Forever!!! <<