osword.h
Tony van der Hoff
OSLib at mk-net.demon.co.uk
Fri Dec 15 10:29:23 GMT 2000
On Thu, 14 Dec 2000, at 20:16:26, David J. Ruck <druck at freeuk.com> wrote
on the subject "osword.h":
>Couple of mistakes in the osword.h header, not specific to 6.20 but still in
>the latest release.
>
> Currently Should be
>
>#undef OSWordRead_Clock OSWord_ReadClock
>#define OSWordRead_Clock 0xE OSWord_ReadClock 0xE
Yes, you're right, that is mis-named. This is one of the things that the
new StrongHelp manual makes much easier to spot. I'll fix that, thanks.
>#undef OSWordReadClock_LocalString
>#define OSWordReadClock_LocalString 0xE 0x0
>#undef OSWordReadClock_LocalBCD
>#define OSWordReadClock_LocalBCD 0xE 0x1
<snip>
No, You've mis-understood. Those are the SWI numbers that the function
calls, and are correct. I think what you're looking for is the op code
for the specific operation:
oswordreadclock_OP_LOCAL_STRING
oswordreadclock_OP_LOCAL_BCD
etc.
This is another thing that is easier to find in the new manual.
The SWI numbers, although publicly defined, should not be of any real
interest to application programmers.
Thanks for your help, Dave.
Tony
--
Tony van der Hoff | mailto:OSLib at mk-net.demon.co.uk
Buckinghamshire, England | http://www.mk-net.demon.co.uk/oslib/
----------------------------------------------------------------
More information about the oslib-user
mailing list