In message <[EMAIL PROTECTED]>, David Schultz writes: >I believe FILE is required to be a complete type, but it need not >expose any usable fields to applications. For instance,
Well, we may have to dig in the history a bit. BSD has a different stdio implementation than AT&T used, in CFRONT it was known as "BSD stdio". If you look at how some of the printf* family functions are implemented in libc, you will find liberal use of creating FILE's that point to memory buffers etc. The question in my mind is, if this extension ability, and its consequent dependence on the internals of FILE, have been flaunted at USENIX ATC at some point, and thus must be considered a published API. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
