On Thu, Aug 16, 2001 at 06:28:14PM +0800, Orlando Andico wrote (wyy sez):
> On Thu, 16 Aug 2001, Ian C. Sison wrote:
> ..
> > I beg to disagree, and for my defense i put forth the "standard" C
> > function named 'ioctl' \8)
>
> I hardly consider ioctl to be a good example.. in fact IMHO it's a BAD
> example.
>
> man page for RH6.2 (my copy of RH7.1 has no man pages for section 2 for
> some reason..)
>
> --
> CONFORMING TO
> No single standard. Arguments, returns, and semantics of
> ioctl(2) vary according to the device driver in question
> (the call is used as a catch-all for operations that don't
> cleanly fit the Unix stream I/O model). See ioctl_list(2)
> for a list of many of the known ioctl calls. The ioctl
> function call appeared in Version 7 AT&T Unix.
> --
>
hmmm. but, i tend to use this a lot 'ioctl' is like the swiss knife of
systems programming. just look at the header include files and the
'ioctl'...wala....you can control a good number of things. my latest
clash with 'ioctl' was for audio playback and mixer settings.
although, in defense of ian...the 'ioctl' function has a very clean
interface. it is simple to place a number of #ifdef LINUX and macro
the IOCTL() with the real ioctl() in syntax varies from unix to unix.
(this gets a little tiring though) but, i can say it is consistent
enough to be standard and it is standard in linux at least. hehehe.
my $0.00000000002
--------------------------------------
William Emmanuel S. Yu
Ateneo Cervini-Eliazo Networks (ACENT)
email : [EMAIL PROTECTED]
web : http://cersa.admu.edu.ph
phone : 63(2)4266001-5925/5904
GPG : http://sysads.ateneo.net/wyu/wyy.pgp
One man tells a falsehood, a hundred repeat it as true.
PGP signature
