SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-18-2008, 06:29 AM
| ||||
| ||||
 open(2) misinformation ? There seems to be some misinformation on open(2): gaia:~$ man open (...) STANDARDS The open() function conforms to ANSI X3.159-1989 (``ANSI C''), Which is, according to other operating systems man-pages, not true. I've checked NetBSD, FreeBSD and Linux. Further on, if we look at "Advanced Programming in the UNIX environment", from Richard Stevens, we will see a statement like this: "These unbuffered I/O functions are not part of ANSI C, but are part of POSIX.1 and XPG3". Additionally, looking at http://www.nd.edu/~lemmon/courses/UNIX/l3/node3.html, we will see: (...) The standard I/O library for ANSI C ( fopen, fscanf, fprintf, fread, fwrite, {fclose)) use file pointers, while the UNIX I/O library (open, read, write, close, ioctl use file descriptors. (...) And on http://www.delorie.com/djgpp/doc/libc/libc_291.html, there is: (...) Portability not ANSI, POSIX (see note 1) One curious thing, though, is that using -ansi and -pedantic does not make gcc warn about that. -p.      |
Linear Mode
