> First, on calling C functions from assembly, it says:
[...]
> Shouldn't the first one be "call _foo"?
Yes.
> Also, I don't remember where I saw it, I think it was in Concepts, but it
> said to never directly modify the sp register and to always push and
> pop. It said there were complications in a multitasking environment.
That's true in general. This particular case is appropriate.
Note that unless you need to call off to existing, pre-compiled C code from
assembly (or need varargs support :-) that you should make all of your C
code use the _pascal calling convention. The pascal calling convention is
both smaller and faster than the C calling convention. There's a
configuration option for Borland's compilers to tell it to assume either
one of the calling conventions (so you don't have to add the _pascal
modifier to everything).
> Next... In the explaination of error messages...
[...]
> Next... There are a lot of OpenLook things at the end of the death due to
> error messages. Any way to get OpenLook? Also, while on the subject, I
> was looking at \pcgeos\include\send and it mentioned a couple other
> SpecUI's and a bunch of sample apps and said they were released but
> aren't on the SDK. Why are so many files not available?
[...]
OpenLook was the original SpecUI before a deal was made to do Motif instead
(when OpenLook was still a possible winner in the GUI wars :-). When the
switch was made to Motif little or none of the existing software was
renamed.
Things like the Mac SpecUI aren't released a) because there's no
licence to do so and/or b) because they are not fully implemented (i.e.,
they were just "proof of concept" work).
Hope this helps,
John