T
Tony
Let's see... there are 2 C language newsgroups: comp.lang.c and
comp.lang.c.moderated. With only those 2, which by the naming should be
discussions of the same topics but with one being moderated/enforced, well,
OF COURSE anything even remotely C-related is going to end up there. The
cliche joke is: "if it hurts when you do that, don't do that!". Meaning, why
not create branch groups off of comp.lang.c and leave the top level for the
somewhat more esoteric and largely boring language lawyer stuff? Sure, there
will be overlap, but the net result will be expansion of the thoughtspace
regarding USAGE of C, which is good! I don't see the OS groups being a place
to foster those discussions because the focus there is too much on the OS
idiosynchracies rather then that with a C flavor. Deciding what
subcategories to create requires some deep thought is all, which seems
pretty easy. The same applies to the C++ groups and probably moreso since
they probably have more traffic there (I'm not really a C user, but rather a
C++ user, though in the early 1990's, I used C exclusively, but I still find
C relevant).
Here's my "off the top of my head" categorical suggestions:
comp.lang.c.datastructuresandalgos
comp.lang.c.platformspecific
comp.lang.c.industryspecific
comp.lang.c.isostdc
comp.lang.c.misc
I'd even suggest deprecating comp.lang.c over time and migrating to
something like the above tree.
Tony
comp.lang.c.moderated. With only those 2, which by the naming should be
discussions of the same topics but with one being moderated/enforced, well,
OF COURSE anything even remotely C-related is going to end up there. The
cliche joke is: "if it hurts when you do that, don't do that!". Meaning, why
not create branch groups off of comp.lang.c and leave the top level for the
somewhat more esoteric and largely boring language lawyer stuff? Sure, there
will be overlap, but the net result will be expansion of the thoughtspace
regarding USAGE of C, which is good! I don't see the OS groups being a place
to foster those discussions because the focus there is too much on the OS
idiosynchracies rather then that with a C flavor. Deciding what
subcategories to create requires some deep thought is all, which seems
pretty easy. The same applies to the C++ groups and probably moreso since
they probably have more traffic there (I'm not really a C user, but rather a
C++ user, though in the early 1990's, I used C exclusively, but I still find
C relevant).
Here's my "off the top of my head" categorical suggestions:
comp.lang.c.datastructuresandalgos
comp.lang.c.platformspecific
comp.lang.c.industryspecific
comp.lang.c.isostdc
comp.lang.c.misc
I'd even suggest deprecating comp.lang.c over time and migrating to
something like the above tree.
Tony