PATCH-faq.html, c++bugs.html

Nathan Sidwell nathan@acm.org
Thu Feb 18 02:21:00 GMT 1999


Hi,
attached is a patch to the faq and c++bugs html files. The faq did not have a
link from the 'bugs and non-bugs' section to the c++bugs document. I have added
that.
I've altered some of the HTML formatting on the c++bugs to make it look similar
to the faq (footer, rules). I've expanded the blurb at the top to add some
stuff about C++ changing over the years, but now there's a standard. Added an
encouragement to use the latest stable release. I've added a description of g++
not accepting exception specifiers on function pointers.

Enjoy.

nathan
-- 
Dr Nathan Sidwell :: Computer Science Department :: Bristol University
      You can up the bandwidth, but you can't up the speed of light      
nathan@acm.org  http://www.cs.bris.ac.uk/~nathan/  nathan@cs.bris.ac.uk
Title: EGCS C++ Frequently Detected Bugs
Index: wwwdocs/htdocs/faq.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/faq.html,v
retrieving revision 1.103
diff -c -3 -r1.103 faq.html
*** faq.html	1999/02/16 06:54:52	1.103
--- faq.html	1999/02/18 10:16:33
***************
*** 237,243 ****
  
  
  
!  How to report bugs
  There are complete instructions in the egcs info manual, section Bugs.  The
  manual can be read using ` M-x info ' in Emacs, or if the GNU
  info program is installed on your system by
--- 237,243 ----
  
  
  
! How to report bugs
  There are complete instructions in the egcs info manual, section Bugs.  The
  manual can be read using ` M-x info ' in Emacs, or if the GNU
  info program is installed on your system by
***************
*** 819,825 ****
--- 819,830 ----
  following problems with some releases of widely used packages have
  been identified:
  
+ There is a separate list of well-known C++ bugs
+ describing known deficiencies in the C++ compiler . Naturally we'd
+ like that list to be of zero length.
  
+ To report a bug, see How to report bugs .
+ 
  
  FD_ZERO macro
  
***************
*** 1107,1113 ****
  
  
  Return to the EGCS home page
! Last modified:  February 15, 1999
  
  
  
--- 1112,1118 ----
  
  
  Return to the EGCS home page
! Last modified:  February 18, 1999
  
  
  
Index: wwwdocs/htdocs/c++bugs.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/c++bugs.html,v
retrieving revision 1.3
diff -c -3 -r1.3 c++bugs.html
*** c++bugs.html	1999/01/07 13:57:08	1.3
--- c++bugs.html	1999/02/18 10:16:33
***************
*** 3,20 ****
  
  
  
! Frequently reported bugs of the EGCS C++ compiler
  
! This is the list of bugs in g++ that are reported very often, yet not
  fixed. While it is certainly better to fix bugs instead of documenting
  them, this document might save people the effort of writing a bug
  report when the bug is already well-known.
  
! There are many reasons why reported bugs don't get fix. It might be
! difficult to fix, or fixing it might break compatibility. Often,
  reports get a low priority when there is a simple work-around. In
! particular, bugs caused by invalid C++ code have a simple work-around:
! Fix the code.
  
  G++ allows to access private structs
  egcs 1.1 incorrectly accepts code like
--- 3,35 ----
  
  
  
! Frequently reported bugs of the EGCS C++ compiler
  
! The latest version of this document is always available at http://egcs.cygnus.com/c++bugs.html .
! 
! This is the list of bugs in g++ that are reported very often, yet not
  fixed. While it is certainly better to fix bugs instead of documenting
  them, this document might save people the effort of writing a bug
  report when the bug is already well-known.
+ How to report bugs tells you how to report a
+ bug.
  
! There are many reasons why reported bugs don't get fixed. It might
! be difficult to fix, or fixing it might break compatibility. Often,
  reports get a low priority when there is a simple work-around. In
! particular, bugs caused by invalid C++ code have a simple work-around,
! fix the code . Now that there is an agreed ISO/ANSI standard
! for C++, the compiler has a definitive document to adhere to. Earlier
! versions might have accepted source code that is no longer
! C++. This means that code which might have `worked' in a previous
! version, is now rejected. You should update your code to be C++.
! 
! You should try to use the latest stable release of the EGCS C++
! compiler. This is currently 1.1. Many commonly reported bugs in earlier
! releases are fixed in that version. 
! 
! 
  
  G++ allows to access private structs
  egcs 1.1 incorrectly accepts code like
***************
*** 123,127 ****
--- 138,157 ----
  This bug is fixed in egcs 1.1.1 (2.91.60), as well as in the
  development branch (2.92.21 and later)
  
+ Exception specifiers on function pointers
+ Although allowed by the standard, egcs 1.1 will report an
+ 'invalid exception specifications' error if you
+ declare a function pointer with an exception specification.
+ void (*fptr)() throw();
+ 
+ 
+ 
+ 
+ Return to the EGCS home page  
+ Return to the EGCS FAQ
+ Last modified:  February 18, 1999
+ 
+ 
  
  



More information about the Gcc-patches mailing list