What does POSIX say about all of this? My quick reaction is that this
is all rather messy.
Is there any good reason to just not use the 64-bit calls all the time
if they exist?
On NetBSD, lseek(2) is said to be POSIX compliant:
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
Hi Kevin,
On Fri, 2006-09-08 at 09:17 +1000, Kevin Ryde wrote:
> Actually instantiating a port from a descriptor isn't documented, so
> it's possible no applications are using the C port type stuff at all!
Guile-gnome's gnome-vfs wrapper uses it. You can make a SCM port out of
a gnome-vfs handle
Greg Troxel <[EMAIL PROTECTED]> writes:
>
> Is there any good reason to just not use the 64-bit calls all the time
> if they exist?
I did that for file descriptors and filenames, the ports are the
hold-out.
> What does Solaris do? I looked on the web and couldn't figure out if
> one has to use d
Rob Browning <[EMAIL PROTECTED]> writes:
>
> I believe a while back I wondered if we might have trouble with
> pthreads and fork unless we were very careful, and I'm beginning to
> wonder again.
Ahh, that sounds likely. If mutexes are unusable once forked then
that'd hurt the gc trying to get all