32 bit file handles
Ralph Corderoy
ralph at inputplus.demon.co.uk
Mon Nov 12 10:55:01 GMT 2001
Hi,
> > Howsabout
> >
> > #define osfind_openin(flags, file_name, path) \
> > osfind_openinw(flags, file_name, path)
> >
> > then later
> >
> > os_f (osfind_openin)(osfind_flags flags, char const *file_name,
> > char const *path);
>
> I think I understand your intentions, but I'm not sure that I
> understand how you're proposing to implement it.
>
> If I read you correctly, you're suggesting modifying osfind.h.
> Remember, that these headers are autogenerated by DefMod, so any such
> change would have to be via DefMod, and carry across throughout
> OSLib.
Yes, I was suggesting DefMod change.
> Limiting this is the reasoning behind introducing the xxx32.h
> maually-generated extensions.
OK.
> I also believe that it is excessively restrictive to constrain the
> number of parameters in a call by defining them in a macro.
Agreed. If any of the C functions that need renaming use ellipses then
it isn't a goer as this isn't C99.
> I know my proposal involves modifying DefMod, but I believe it is
> less far-reaching than what you're suggesting.
OK. I was thinking that only the C functions that needed renaming
would be parenthesised, either by an attribute in the grammar or a
separate list of function names, and that xxx32.h could also be
generated by DefMod. Apologies if I've the end of completely the wrong
stick.
Ralph.
More information about the oslib-team
mailing list