[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OMG!



Im Artikel <3AEDC60F.D1E1AFEC@inetnebr.com> schrieb "Roy and/or Janet
Miller" <millers@inetnebr.com>:


> Byron Desnoyers Winmill wrote:
> 
>>
>> Amazing, $31 (presumably American) for a piece of software.  The Apple
>> II sound pretty uneconomical when you compare it to 68k Macintosh
>> computers.  Recent examples (in *Canadian* funds)
> It simply means that collectors of Apple II software are willing to pay
> more for older items than people are willing to pay for more recent
> Macintosh (but still old and used) software. I'd dare say that a 1989
> Mustang isn't nearly as valuable as a 1966.
> 
>>
>>  - CodeWarrior 9 Gold, $75
>>    ANSI C, ANSI C++, Pascal, Java; Mac II or better (fairly cheap
>>    machines).  ByteWorks offers a not-quite-ANSI C
> It is fully ANSI compliant. However, after it was written and on the
> market, the ANSI standards were changed. Put a date on your ANSI.

I disagree that Orca C is or ever was fully ANSI compliant. At least,
what I have isn't. It has, for example, no support for signals. the
manual dismisses this lack by saying that signals are only important
for Unix and have no relevance for the IIgs.

Everything in the ANSI standard, however, is supposed to be supported
cross-platform. Just because GS/OS doesn't have Unix style signals
doesn't mean that the program shouldn't be able send a signal to
itself.

Anyway, my biggest problem with Orca C wasn't ever the small deviations
from ANSI, rather it was the buggy code generation. It's been a while
but I seem to remember having quite a bit of trouble using function
pointers.

-- 
sheldon@semanticedge.com  "The term (denotation t) denotes the object denoted
                           by the object denoted by t." -- KIF