This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Problem with private methods
- From: Reichelt <reichelt at igpm dot rwth-aachen dot de>
- To: sten dot hultman at cgey dot com, gcc-help at gcc dot gnu dot org
- Date: Fri, 8 Feb 2002 19:57:34 +0100
- Subject: Re: Problem with private methods
Hello!
> I have encountered a problem when turning from aCC to gcc 3.0.3 on
> HP-UX11.00.
>
> I enclose a short samle and the error messages.
> It works with no problem on aCC.
> I can't see why the streambuf methods are private in this context.or
> anyo
> Greatful for any hint !
>
> Kindest regards
> Sten Hultman
It's intentional that the copy-constructor and operator= of streambuf
are private. A look at the streambuf header unveils:
----------------snip here---------------------
#ifdef _GLIBCPP_RESOLVE_LIB_DEFECTS
// Side effect of DR 50.
private:
basic_streambuf(const __streambuf_type&);
__streambuf_type&
operator=(const __streambuf_type&);
#endif
----------------snip here---------------------
The explanation can be found in DR (defect report) 50:
http://gcc.gnu.org/onlinedocs/libstdc++/ext/lwg-defects.html#50
Greetings,
Volker Reichelt