Subject: Re: ftruncate & truncate prototypes &
To: None <jtc@cygnus.com>
From: Thorsten Lockert <tholo@SigmaSoft.COM>
List: tech-userlevel
Date: 04/17/1995 22:02:37
------- =_aaaaaaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7888.798181357.1@gandalf.sigmasoft.com>

> I noticed that our <sys/types.h> header provides a prototype for
> lseek().  This helps programs that don't #include <unistd.h> get
> lseeks()'s prototype (since our off_t is now 64 bits). 
> 
> Should we do the same for truncate() and ftruncate()?

I'd rather see the prototype moved to <unistd.h>...  But I can see
why having it (and perhaps a couple more) in <sys/types.h> even though
they do not really belong there...

Does ANSI / POSIX / SVID / whatever have anything to say about this?

Thorsten

------- =_aaaaaaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7888.798181357.2@gandalf.sigmasoft.com>
Content-Description: Signature

--
Thorsten Lockert        | postmaster@sigmasoft.com | Universe, n.:
1262 Golden Gate Avenue | hostmaster@sigmasoft.com |         The problem.
San Francisco, CA 94115 | tholo@sigmasoft.com      |

------- =_aaaaaaaaaa0--