Re: ORCA/C is a horrible compiler

[vandry@CAM.ORG (Phillip Vandry)]

> And why did you _NEED_ to patch the compiler?  This sounds very very very
> peculiar if you really needed to do these things to make it work.

The compiler runs silently unless its input is from .CONSOLE. Of course it
usually is under ORCA. It is not in GNO. The patch removes this check.

Aside from enabling output in GNO without having to include "<.console" on
the command line, it also disables an illogical restriction. I don't see
why the compiler should run silently just because input is not from .CONSOLE,
even in ORCA.

> >While I was at it I removed the twirly cursor because it is extremely
> >annoying when compiling in the background.
>
> Does taking out the twirly cursor improve speed noticably? I highly doubt
> it but it's worth asking for.  (Your removing of the twirly cursor doesn't
> make it so you can't stop output by just hitting space does it?)

No, it doesn't, but it would be easy to come up with another patch. As for
the speed, essentially, two calls to ConsoleOut are removed every time the
twirly would have changed. Not enough to be noticeable.

> oh ok, I guess the init question answers my first question..  WHAT is the
> init???

It does what GNO 1.1 will do (so don't install it if you have GNO 1.1). If
somebody calls GetStdRefNum, first it checks for GNO. If GNO is not present,
it passes the call along to GS/OS. If GNO is present it simply returns 1, 2
or 3 as aproppriate.
 ______________________________________________________________________
|~~~~~~~~~~~~~~~~|~~~~~~~~~~~~~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| Phillip Vandry | Vandry@Cam.Org | Suicide (n.): What to do if Macs   |
|________________|________________|_______________take over the world__|
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~