Path: utzoo!telly!attcan!uunet!tut.cis.ohio-state.edu!YAHI.STANFORD.EDU!tiemann From: tiemann@YAHI.STANFORD.EDU (Michael Tiemann) Newsgroups: gnu.g++ Subject: Gnu Gbugs? Message-ID: <8905161613.AA01825@yahi.stanford.edu> Date: 16 May 89 16:13:10 GMT References: <1887@ektools.UUCP> Sender: daemon@tut.cis.ohio-state.edu Reply-To: tiemann@lurch.stanford.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 114 Path: mit-eddie!rutgers!rochester!kodak!ektools!randolph From: ektools!randolph@ai.mit.edu (Gary L. Randolph) Newsgroups: comp.lang.c++ Date: 16 May 89 14:22:54 GMT Sender: randolph@ektools.mit.edu (Gary L. Randolph) Organization: Eastman Kodak, Dept. 47, Rochester N.Y. Lines: 105 Apparently-To: lang-c++-netnews-dist@wheaties.ai.mit.edu I have been using both AT&T's cfront and Gnu's g++ compiler. My copy of Gnu's g++ is about 3 months old so some of what follows may be dated. It is. Are the following current Gnu gbugs??? 1.) The exact match rule that Stroustrup (pgs. 122 and 290) discusses does not work. The following was used as a test: overload show; void show(int x) { cout<<"\nThe integer is: "<