Date: Wed, 16 Oct 2002 09:29:47 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Maxim Sobolev <sobomax@FreeBSD.ORG> Cc: Robert Watson <rwatson@FreeBSD.ORG>, "Danny J. Zerkel" <dzerkel@columbus.rr.com>, "Vladimir B. Grebenschikov,Moscow,408-7227,123-4567,Some-info" <vova@express.ru>, freebsd-arch@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: short uid/gid Message-ID: <3DAD93FB.78324E0E@mindspring.com> References: <Pine.NEB.3.96L.1021016004135.36711H-100000@fledge.watson.org> <3DAD2B79.AD5412CA@mindspring.com> <20021016093048.GB10908@vega.vega.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DAD93FB.78324E0E>