8 bit os_f handles
Jonathan Coxhead
jonathan at doves.demon.co.uk
Tue Apr 4 02:55:08 BST 2000
John wrote,
| nobody is *forced* to use a new version of OSLib.
| Programmer/user of OSLib is free to go for a new version if he
wants
| so. Where is the pressure ? We're not in the M$ world after all
where
| everybody is being pushed to go for the latest version !?!
The pressure arises because you may wish to use new bits of OSlib
that are completely unrelated to file handles. For example, you may
want to pick up the ScrollList fixes that Tom's just added. You
should be able to do this safely, without wondering whether your
"upgrade" is actually going to break your software (because you rely
on 8-bit |os_f|, for example), which would make it more of a
"downgrade", really.
| Again, what's the problem specifying that the next version of OSLib
| has os_f defined as 32 bit as consequence of a *bug* fix in OSLib
and
| adding an appropriate warning that the source needs to be checked
that
| it doesn't fall over the fact the os_f is now 32 bit (which needs
to
| happen anyway when he wants to change os_f to os_w) ?
Umm ... haven't we covered this already?
/|
o o o (_|/
/|
(_/
More information about the oslib-user
mailing list