[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: State of the Woody


Please explain what kinds of things don't compile. 

You don't tell me enough for me to tell if I can be helpful, but here
is a shot in the dark. I apologize for posting this if not apropos. 

My students had a hard time with namespaces.  If your problem is
namespaces then names defined in headers without extensions such as
iostream that were available in the corresponding header with a .h
such as iostream.h are now placed in namespace std when you #include
<iostream> The symptom is names, such as cout for example, not

Then you have to either qualify with std::cout, for example, or in a
function that uses these, place a using namespace std;  or using
std::cout;  where you replace cout by any name that you want made

I hope this is not off base and that it help. I look forward to a
STABLE standard compliant g++ and libC++. 


On Wed, 20 Dec 2000, Ben Collins wrote:

> On Tue, Dec 19, 2000 at 10:47:24PM +0100, Matthias Klose wrote:
> > Marco d'Itri writes:
> >  > On Dec 19, "Marcelo E. Magallon" <mmagallo@debian.org> wrote:
> >  > 
> >  >  > I hope noone is seriously considering getting gcc 3.0 into woody given
> >  >  > the above time schedule.  gcc 3.0 is hell when it comes to C++.  It
> >  > What about shipping gcc 3.0 for C and a more stable release for C++?
> >  > We did that at egcs time.
> > 
> > ... and we got much confusion which C compiler to use, when using g++ ...
> > what is more "stable" than gcc-3.0 for C++? 
> > 
> > - Perhaps in 2.95.x you already know the bugs.
> > + libstdc++ independent from glibc.
> > + standard compliant (backward headers as well).
> FYI, I can't get any current C++ applications to compile with libstdc++-v3
> on ppc and sparc. How does one allow backward compatible builds?
> -- 
>  -----------=======-=-======-=========-----------=====------------=-=------
> /  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
> `  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
>  `---=========------=======-------------=-=-----=-===-======-------=--=---'
> --  
> To UNSUBSCRIBE, email to debian-toolchain-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: