8 bit os_f handles
David J. Ruck
druck at freeuk.com
Wed Mar 29 02:24:34 BST 2000
On Wed 29 Mar, Jonathan Coxhead wrote:
> Tom wrote,
>
> | Surely the
> | point here though is that any code using os_f will have to include
> | os.h either directly or indirectly, and the Makefile would normally
> | have a dependency on that for any source file using os_f.
>
> Not if it's in a 3rd-party library. Or if you just decide, for
> reasons of your own, that you want to relink, but not recompile.
>
> And in any case, if the compatibility-breakers got their way,
> there might be no changes in "os.h", so even if you did a make, it
> wouldn't show up on the radar.
What? Where else is os_f defined?
This is getting rediculous. I am trying to warn everyone of an imminant
problem which effects OSLib, not start some sort of personal vendetta.
I've already had to fork my own version of OSLib to fix os_f, now I have the
extra additional and unecessary task of maintaining it. Thank you very much.
---Dave
--
______________________________________________________________________
David J. Ruck Phone: 07974 108301 Email: druck at freeuk.com
______________________________________________________________________
More information about the oslib-user
mailing list