GV>How about defining an extended FCB data structure, that may
>contain parameters, commands, result codes, pointers, etc?
NS> No please!!! I'm very happy with the FCB to FH update of DOS2,
> and I want to continue in this way!
I guess I shouldn't have used the name FCB; so, let's just say
a function "structure" or "record". An API Control Block (ACB)?
It wouldn't need to resemble old FCBs in any way. It could hold
the full file path and name, File Handle, attributes, process ID
or ownership, priority codes, etc.
There are operating systems that use structures for interfacing
to the API. Instead of loading CPU registers with everything, a
pointer is used to reference a memory-based record.
This technique can provide backward compatibility. Old API calls
would operate on registers, new API calls could also access the
extended functions record.
Greg_
http://www.netcom.ca/~telic
1998.Nov.14, Toronto, Canada
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
