> Hm, I didn't know that "export" is unsupported in g++. Maybe you know what
> compilers support it (Borland, Watcom)? (AFAIR, MSDEV does not.)
To my knowledge, none supports it. I think IBM Visual Age accepts it,
but processes it incorrectly in some cases.
> Anyway, I am suspiciously look at "ex
Hello, maintainers.
I don't know what the package has the bug, so I write to 3 maintainers
(packages: menu, dwww, libstdc++3-doc).
I have the following versions of these packages installed on my system:
ii menu 2.1.5-10 provides update-menus functions for some app
ii dwww
That makes sense, thanks. That's the key piece I was missing.
--
John R. DailyProgeny Linux Systems
Consultant [EMAIL PROTECTED]
Master of the ephemeral epiphany
Package: gcc272
Version: 2.7.2.3-18
Severity: grave
Since unstable/testing does no longer include kernel 2.0.x (and these
kernels won't work with the modutils in unstable/testing) it's in
my opinion time to remove gcc272 from unstable.
I've set the severity to be RC so that this doesn't be forgo
"Martin v. Loewis" wrote:
> > > > Why is it happening? Is it so because of more complex templates in
> > > > recent
> > > > libstdc++?
> > >
> > > If you are asking for compilation speed, yes, the main cause it that
> > > libstdc++ consists of many more templates now. If you are asking for a
> >
> What I do not understand is why the compiler does _not_ find
> ambiguity when the C++ class header is slimmed down to just the
> necessary parts: the operator overload and a constructor.
Because you've removed the ambiguity in simple.h. If you add the line
operator const char*()const;
back
6 matches
Mail list logo