Maxim Sobolev wrote: > > You could also simply use non-intersecting cmd parameter values > > for the new calls, which avaids the special flag, and leaves the > > backward compatability without adding grundles of new system calls. > > What about source-level compatibility, which IMO is a good thing, > at least if it doesn't add too much complexity (it clearly doesn't > in this case)? Also, handling single flag should be easier from > the coding perspective than a load of new values, after all > we can do something like: > > #define IPC_STAT_OLD 0xXY > #define IPC_SET_OLD 0xZW > [...] > > #define IPC_64 0x100 > > #define IPC_STAT (IPC_STAT_OLD | IPC_64) > #define IPC_SET (IPC_SET_OLD | IPC_64) > [...] > > Which automagically will bring 64-version of syscalls after > recompilation, while retaining ABI compatibility.
This is exactly what I was suggesting. In Linux, you do this manually (read their header files). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
