Xref: utzoo gnu.g++.help:222 comp.lang.c++:10698 Path: utzoo!utgpu!cunews!bnrgate!uunet!peregrine!elroy.jpl.nasa.gov!usc!cs.utexas.edu!tut.cis.ohio-state.edu!eng.sun.com!tiemann From: tiemann@eng.sun.com (Michael Tiemann) Newsgroups: gnu.g++.help,comp.lang.c++ Subject: Anyone for decoupling GNU and c.l.c++? Message-ID: <9012051730.AA14088@teacake.Eng.Sun.COM> Date: 5 Dec 90 17:30:04 GMT References: <59548@microsoft.UUCP> Sender: daemon@tut.cis.ohio-state.edu Reply-To: tiemann@cygnus.com Followup-To: gnu.g++.help Organization: Cygnus Support (+1 415 322 3811) Lines: 42 There is a reason why the gnu.g++ and comp.lang.c++ newsgroups were linked. It was not, as Jim ADCOCK suggests, because one or the other was not strong enough to stand on its own readership. Rather, it was because many people (a vast majority of those who voted) wanted to share experiences and information between the two groups. Here are some examples where multiple inheritance (for newsgroups) is useful: 1. A naive G++ user has a question about overloading operator+. Should s/he ask in the g++ forum or the comp.lang.c++ forum? Usually the answer is unclear, so people cross-post. As a matter of fact, one of the reasons that these groups were merged was because there was so much cross-posting going on. 2. An unspecified C++ user finds that cfront and g++ have different behavior for a complicated inheritance lattice. Both results are unexpected (this has happened). Where does s/he post? 3. A C++ expert has just released a cool, freely redistributable C++ interface to X/NeWS. Where should the announcement go? 4. A bored graduate student hears about the above library, but doesn't know where to get it. To which group should he pose his request for information? The list goes on and on. Everybody has their own quirks about what they will and will not tolerate about people's postings. Some people get upset when they see postings about how clever they were at painting themselves into a 640K address space. Some people are dismayed by other's blithe acceptance of UNIX. If it absolutely ruins your day that somebody doesn't understand how to overload operator+, how segmented architectures are really better than large linear address spaces, or how Apple and Lotus are taking away programmer's freedoms, I believe that there is a newsreading service which, for a small fee, will delete these messages before you have a chance to read them, and you need never know they were ever written. In the mean time, please don't ask to have everybody's service disconnected because you don't like yours. Michael Brought to you by Super Global Mega Corp .com