This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: elided copy constructors
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: elided copy constructors
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Mon, 29 Mar 1999 22:49:58 +0200 (MET DST)
- cc: egcs at egcs dot cygnus dot com, egcs-patches at egcs dot cygnus dot com
On Sun, 28 Mar 1999, Mark Mitchell wrote:
> Here's what I put it.
Thanks! I have fixed a small "typo" and made the second option a bit
more optimistic, according to my personal experience:
alphard[56]:~% ls -la Bugreports/egcs* | wc -l
55
alphard[57]:~% ls -la Bugreports/egcs* | grep -v fixed | wc -l
8
I.e., only 8 bugs out of 55 I have reported have not been fixed yet. :-)
Gerald
Index: faq.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/faq.html,v
retrieving revision 1.117
diff -c -3 -p -r1.117 faq.html
*** faq.html 1999/03/28 09:45:26 1.117
--- faq.html 1999/03/29 20:46:01
*************** disadvantages.
*** 301,312 ****
<li>Report the problem to egcs-bugs and hope that someone will be kind
enough to fix it for you. While this is certainly possible, and
! sometimes happens, there is no guarantee that it will. You should
not expect the same response from egcs-bugs that you would see
from a commercial support organization since the people who read
egcs-bugs, if they choose to help you, will be volunteering their
! time. This alternative will work best if follow the directions on
! <a href="#bugreport">submitting bugreports</a>.
<li>Fix it yourself. This alternative will probably bring results,
if you work hard enough, but will probably take a lot of time,
--- 301,312 ----
<li>Report the problem to egcs-bugs and hope that someone will be kind
enough to fix it for you. While this is certainly possible, and
! often happens, there is no guarantee that it will. You should
not expect the same response from egcs-bugs that you would see
from a commercial support organization since the people who read
egcs-bugs, if they choose to help you, will be volunteering their
! time. This alternative will work best if you follow the directions
! on <a href="#bugreport">submitting bugreports</a>.
<li>Fix it yourself. This alternative will probably bring results,
if you work hard enough, but will probably take a lot of time,
*************** only be necessary if you are building an
*** 1168,1174 ****
<p><a href="index.html">Return to the EGCS home page</a>
! <p><i>Last modified: March 23, 1999</i>
<!--#include virtual="/glimpsebox.html"-->
</body>
--- 1168,1174 ----
<p><a href="index.html">Return to the EGCS home page</a>
! <p><i>Last modified: March 29, 1999</i>
<!--#include virtual="/glimpsebox.html"-->
</body>