Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!elroy.jpl.nasa.gov!decwrl!mcnc!ecsgate!ecsvax!uncw!session
From: session@uncw.UUCP (Zack C. Sessions)
Newsgroups: comp.lang.c
Subject: Re: file descriptor vs file handle
Message-ID: <1046@uncw.UUCP>
Date: 5 Mar 91 19:15:49 GMT
References: <90361.145855COS99291@ufrj.bitnet> <27C9CB35.5F7@wilbur.coyote.trw.com> <1021@uncw.UUCP> <1991Mar4.125722.9059@informatik.uni-erlangen.de>
Organization: Univ. of North Carolina at Wilmington
Lines: 21

richter@immd4.informatik.uni-erlangen.de (Joachim Richter) writes:

>In article <1021@uncw.UUCP> session@uncw.UUCP (Zack C. Sessions) writes:
>[13 lines deleted]
>>of it's data structure. Files which you access with File Descriptors
>>use the fopen, printf and scanf constructs, fread, fwrite, and
>>fclose (plus others). The distinct difference between the two is


>Is it really true, that you don't know that fopen returns a FILE * ?

No, not true. I was using not exactly correct terminology, but
I was trying to get the point across to a question which really wasn't
"asked right" anyway. What I was referring to as a File Descriptor
is what my C manual calls a "pointer to a file structure (file
pointer)". The "other" was IO is performed with my C compiler is
in "raw" mode designed to work with direct system calls. It uses
an int variable to store what it calls the "path number".

Zack Sessions
session@uncw.UUCP