oswordreadclock_utc

[Tony van der Hoff]

On 9 Jul 2001, David J. Ruck <druck at freeuk.com> wrote:

> I think it does need to be made clear in the headers and StrongHelp that
> data blocks should contain the relevant reason code, after all it mentions
> register contents during the call, so not mentioning data can lead to
> problems like mine. I dont think I can be the only person this has happened
> to - if so I'll let it lie :-)
> 

Well, I've done it, for one :-)

OK, I've added a comment to the description for the SWIS
derived from OSWord_ReadClock, OSWord_WriteClock, and
OSWord_Pointer. 

I don't really want to go through all the API manually searching for
similar cases, but can anyone point me at other SWIs where a sub-reason code
is embedded in a parameter block?

-- 
Tony van der Hoff         | MailTo:tony at mk-net.demon.co.uk
                          | MailTo:avanderhoff at iee.org
Buckinghamshire, England  | http:www.mk-net.demon.co.uk