Xref: utzoo gnu.g++.help:5 comp.lang.c++:9910 Path: utzoo!telly!attcan!uunet!crdgw1!rpi!zaphod.mps.ohio-state.edu!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!AI.MIT.EDU!tower From: tower@AI.MIT.EDU (Leonard H. Tower Jr.) Newsgroups: gnu.g++.help,comp.lang.c++ Subject: where to discussi possible new features Message-ID: <9010111343.AA00708@apple-gunkies.ai.mit.edu> Date: 11 Oct 90 13:43:13 GMT References: Sender: daemon@tut.cis.ohio-state.edu Reply-To: tower@ai.mit.edu Followup-To: gnu.g++.help Distribution: gnu Organization: Project GNU, Free Software Foundation, 675 Massachusetts Ave., Cambridge, MA 02139, USA +1 (617) 876-3296 Lines: 30 Date: 10 Oct 90 21:42:41 GMT From: hagerman@o.gp.cs.cmu.edu (John Hagerman) Organization: Carnegie Mellon University P.S. So is this now the correct group in which to advance for discussion suggested improvements to G++? If a consensus is reached, how should the suggestion be forwarded to the developer? -- hagerman@ece.cmu.edu If you have a simple suggestion for an improvement, just send it to bug-g++@prep.ai.mit.edu (aka newsgroup gnu.g++.bug). It will help if you also include working code. Code proves your idea out and will increase the chance that your idea will be adopted sooner. Be careful about free-ranging discussions. If the volume on this list gets too high, people (too often the most qualified to help) will stop reading it. If you feel an idea will need a lot of discussion, it would be best to ask people to e-mail you their thoughts, and conduct the discussion via e-mail outside this list. In effect, setting up a short-term temporary mailing list. When the group has come to a consensus, send a report into bug-g++. If the idea changes enough to need input from more people, you can post a summary of what's happened, and ask if anyone else wants to join in via e-mail outside this list. thanx -len (aka help-g++-request@prep.ai.mit.edu)