Re: key64_t? ino64_t?

[Christopher Faylor <cgf at redhat dot com>]

On Sat, May 10, 2003 at 08:05:35PM +0200, Corinna Vinschen wrote:
>On Sat, May 10, 2003 at 02:04:07PM -0400, Christopher Faylor wrote:
>> On Sat, May 10, 2003 at 07:40:55PM +0200, Corinna Vinschen wrote:
>> >This is important to decide and to code ASAP, to get out 1.5.0 finally.
>> >
>> >Do we want a 64 bit key_t in Cygwin?  Yes?  No?  Who will do the changes?
>> 
>> I'd say yes.  The changes should be trivial compared to ino_t.
>> 
>> >Do we want a 64 bit ino_t in Cygwin?  Yes?  No?  Who will do the changes?
>> >(Probably me in this case).
>> 
>> Did you see my email to cygwin?  I said I had most of the changes done, AFAICT.
>
>Yeah, just too late. :-)

Oddly enough, the tricky part here seems to be dirent.h.

Btw, one way to get a unique per-system key value might be to use a
GlobalAtom.  There are resource leak problems with that but I wonder if
it is worth considering.  Atoms are only 32 bits, fwiw.

cgf