Quote:
>So what does this mean,
>That discussing sockets in c programming is off the board, or that from
>C there is no way to program for sockets?
The former. There is a way to use sockets from C; however there are also ways
to use sockets from Perl,
fortran, Ada, TCL and other languages. Sockets are
language-independent operating system objects.
But that's beside the point, because files are also such system objects,
yet file I/O (using the standard C library) is within the scope of the language.
What it boils down to is this: the C language standard doesn't define
any sort of library interface for networking, and hence such an interface
can exist only as a system-specific extension to the language.
We don't discuss extensions at length, because the possibilities for extensions
are endless, and call for a lot of domain specific knowledge that is irrelevant
to C. If we started discussing 3D rendering libraries for C programmers, we
would soon be lost in computer graphics jargon having little to do with C,
wouldn't we? Classical optics, atmospheric effects, interpolated shading,
radiosity, image mapping, NURBs... Great stuff, but really not suited
for a newsgroup called comp.lang.c. This sort of discussion would only
split the newsgroup participants, who otherwise share a common interest
in the C language, into small factions.
There is a legitimate need for newsgroup that is dedicated to the C language,
rather than specific problem domains where the C language can be put to
good use (among other languages, of course). The comp.lang.c hierarchy
meets that need.