Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site cybvax0.UUCP
Path: utzoo!linus!decvax!genrad!mit-eddie!cybvax0!aug
From: aug@cybvax0.UUCP (Alan Green)
Newsgroups: net.unix-wizards
Subject: Q: lseek returns long or int? (BSD 4.2)
Message-ID: <119@cybvax0.UUCP>
Date: Mon, 10-Sep-84 22:40:36 EDT
Article-I.D.: cybvax0.119
Posted: Mon Sep 10 22:40:36 1984
Date-Received: Sun, 16-Sep-84 10:29:01 EDT
Organization: Cybermation, Inc., Cambridge, MA
Lines: 33

[ What is a blank line eater?  Does it eat the first line? ]

Documentation (BSD 4.2 UNIX) for lseek(2) under section 'SYNOPSIS':

>    pos = lseek(d, offset, whence)
>    int pos;
>    int d, offset, whence;

Documentation (BSD 4.2 UNIX) for fseek(3S) under section 'SYNOPSIS':

>    fseek(stream, offset, ptrname)
>    FILE *stream;
>    long offset;
>
>    long ftell(stream)
>    FILE *stream;

	Does lseek return a long or an int, and is the argument offset a long
or an 'int'.  (On other machines it returns a long)

	I realize a long and an int are the same on a VAX (the machine I use):
but, lint considers them different.

	Does any know of a machine where a long and an int are different AND
lseek (or fseek) returns an int?


		Please, reply via Mail
		Thanks in advance,
		Alan Green

aug!cybvax0!mit-eddie!???	(I don't know my full address, how do I figure
				 it out?)