I'm build with -wx, but am getting

"absolute_path_test\absolute_path_test.cpp(40) : Warning 18: implied return of __uninitialized_copy_aux at closing '}' does not return value"

which is killing my build. Without changing STLs or editing the STL that comes with the compiler, I need to get rid of this warning.

Is there a way to specify to the compiler to suppress certain warnings?

TAI

Matthew

In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson says...

>Is there a way to specify to the compiler to suppress certain warnings?

-w[errno]

like -w18

Richard

Brilliant.

Thanks for that. :)

(Another case of not seeing the wood for the trees, <blush>)

"Richard Grant" <fractal@clark.net> wrote in message news:bdn8nm$nr2$1@digitaldaemon.com...
> In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson says...
>
> >Is there a way to specify to the compiler to suppress certain warnings?
>
> -w[errno]
>
> like -w18
>
> Richard
>
>

One other thing ... is there a way to do it in code?

Thanks

"Richard Grant" <fractal@clark.net> wrote in message news:bdn8nm$nr2$1@digitaldaemon.com...
> In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson says...
>
> >Is there a way to specify to the compiler to suppress certain warnings?
>
> -w[errno]
>
> like -w18
>
> Richard
>
>

Uh, fix the code so that it always return a value... :p

Sorry, couldn't help myself...

Regards,
Remko van der Vossen

"Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdnn63$17dq$1@digitaldaemon.com...
> One other thing ... is there a way to do it in code?
>
> Thanks
>
> "Richard Grant" <fractal@clark.net> wrote in message news:bdn8nm$nr2$1@digitaldaemon.com...
> > In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson says...
> >
> > >Is there a way to specify to the compiler to suppress certain warnings?
> >
> > -w[errno]
> >
> > like -w18
> >
> > Richard
> >
> >
>
>

Doing that in my own code doesn't help anyone who then uses the same makefiles for their own downloaded versions of DMC++, with the flawed STL files.

If you mean fix the STL files at source, then I guess that's up to Walter ...

"Wichetael" <wichetael@gmx.net> wrote in message news:bdq5ub$10i5$1@digitaldaemon.com...
> Uh, fix the code so that it always return a value... :p
>
> Sorry, couldn't help myself...
>
> Regards,
> Remko van der Vossen
>
> "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdnn63$17dq$1@digitaldaemon.com...
> > One other thing ... is there a way to do it in code?
> >
> > Thanks
> >
> > "Richard Grant" <fractal@clark.net> wrote in message news:bdn8nm$nr2$1@digitaldaemon.com...
> > > In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson says...
> > >
> > > >Is there a way to specify to the compiler to suppress certain
warnings?
> > >
> > > -w[errno]
> > >
> > > like -w18
> > >
> > > Richard
> > >
> > >
> >
> >
>
>

How about using STLport instead, I never had any problems with that myself.

Regards,
Remko van der Vossen.

"Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdqf4r$1aar$1@digitaldaemon.com...
> Doing that in my own code doesn't help anyone who then uses the same makefiles for their own downloaded versions of DMC++, with the flawed STL files.
>
> If you mean fix the STL files at source, then I guess that's up to Walter ...
>
> "Wichetael" <wichetael@gmx.net> wrote in message news:bdq5ub$10i5$1@digitaldaemon.com...
> > Uh, fix the code so that it always return a value... :p
> >
> > Sorry, couldn't help myself...
> >
> > Regards,
> > Remko van der Vossen
> >
> > "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdnn63$17dq$1@digitaldaemon.com...
> > > One other thing ... is there a way to do it in code?
> > >
> > > Thanks
> > >
> > > "Richard Grant" <fractal@clark.net> wrote in message news:bdn8nm$nr2$1@digitaldaemon.com...
> > > > In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson says...
> > > >
> > > > >Is there a way to specify to the compiler to suppress certain
> warnings?
> > > >
> > > > -w[errno]
> > > >
> > > > like -w18
> > > >
> > > > Richard
> > > >
> > > >
> > >
> > >
> >
> >
>
>

I do. However I'm currently writing test projects and makefiles for the next release of STLSoft, and they have to be compatible with all reasonable permutations of compilers/libraries.

"Wichetael" <wichetael@gmx.net> wrote in message news:bdr4jg$20vr$1@digitaldaemon.com...
> How about using STLport instead, I never had any problems with that
myself.
>
> Regards,
> Remko van der Vossen.
>
> "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdqf4r$1aar$1@digitaldaemon.com...
> > Doing that in my own code doesn't help anyone who then uses the same makefiles for their own downloaded versions of DMC++, with the flawed
STL
> > files.
> >
> > If you mean fix the STL files at source, then I guess that's up to
Walter
> > ...
> >
> > "Wichetael" <wichetael@gmx.net> wrote in message news:bdq5ub$10i5$1@digitaldaemon.com...
> > > Uh, fix the code so that it always return a value... :p
> > >
> > > Sorry, couldn't help myself...
> > >
> > > Regards,
> > > Remko van der Vossen
> > >
> > > "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdnn63$17dq$1@digitaldaemon.com...
> > > > One other thing ... is there a way to do it in code?
> > > >
> > > > Thanks
> > > >
> > > > "Richard Grant" <fractal@clark.net> wrote in message news:bdn8nm$nr2$1@digitaldaemon.com...
> > > > > In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson
says...
> > > > >
> > > > > >Is there a way to specify to the compiler to suppress certain
> > warnings?
> > > > >
> > > > > -w[errno]
> > > > >
> > > > > like -w18
> > > > >
> > > > > Richard
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Then don't support SGI's STL. Simple!

=P


"Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdr958$2572$1@digitaldaemon.com...
> I do. However I'm currently writing test projects and makefiles for the
next
> release of STLSoft, and they have to be compatible with all reasonable permutations of compilers/libraries.
>
> "Wichetael" <wichetael@gmx.net> wrote in message news:bdr4jg$20vr$1@digitaldaemon.com...
> > How about using STLport instead, I never had any problems with that
> myself.
> >
> > Regards,
> > Remko van der Vossen.
> >
> > "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdqf4r$1aar$1@digitaldaemon.com...
> > > Doing that in my own code doesn't help anyone who then uses the same makefiles for their own downloaded versions of DMC++, with the flawed
> STL
> > > files.
> > >
> > > If you mean fix the STL files at source, then I guess that's up to
> Walter
> > > ...
> > >
> > > "Wichetael" <wichetael@gmx.net> wrote in message news:bdq5ub$10i5$1@digitaldaemon.com...
> > > > Uh, fix the code so that it always return a value... :p
> > > >
> > > > Sorry, couldn't help myself...
> > > >
> > > > Regards,
> > > > Remko van der Vossen
> > > >
> > > > "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdnn63$17dq$1@digitaldaemon.com...
> > > > > One other thing ... is there a way to do it in code?
> > > > >
> > > > > Thanks
> > > > >
> > > > > "Richard Grant" <fractal@clark.net> wrote in message news:bdn8nm$nr2$1@digitaldaemon.com...
> > > > > > In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson
> says...
> > > > > >
> > > > > > >Is there a way to specify to the compiler to suppress certain
> > > warnings?
> > > > > >
> > > > > > -w[errno]
> > > > > >
> > > > > > like -w18
> > > > > >
> > > > > > Richard
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

STLSoft supports DMC++, and DMC++ supports SGI & STLport, so STLSoft must do also.

"Greg Peet" <admin@gregpeet.com> wrote in message news:bdt2r2$u2h$1@digitaldaemon.com...
> Then don't support SGI's STL. Simple!
>
> =P
>
>
> "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdr958$2572$1@digitaldaemon.com...
> > I do. However I'm currently writing test projects and makefiles for the
> next
> > release of STLSoft, and they have to be compatible with all reasonable permutations of compilers/libraries.
> >
> > "Wichetael" <wichetael@gmx.net> wrote in message news:bdr4jg$20vr$1@digitaldaemon.com...
> > > How about using STLport instead, I never had any problems with that
> > myself.
> > >
> > > Regards,
> > > Remko van der Vossen.
> > >
> > > "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdqf4r$1aar$1@digitaldaemon.com...
> > > > Doing that in my own code doesn't help anyone who then uses the same makefiles for their own downloaded versions of DMC++, with the
flawed
> > STL
> > > > files.
> > > >
> > > > If you mean fix the STL files at source, then I guess that's up to
> > Walter
> > > > ...
> > > >
> > > > "Wichetael" <wichetael@gmx.net> wrote in message news:bdq5ub$10i5$1@digitaldaemon.com...
> > > > > Uh, fix the code so that it always return a value... :p
> > > > >
> > > > > Sorry, couldn't help myself...
> > > > >
> > > > > Regards,
> > > > > Remko van der Vossen
> > > > >
> > > > > "Matthew Wilson" <matthew@stlsoft.org> wrote in message news:bdnn63$17dq$1@digitaldaemon.com...
> > > > > > One other thing ... is there a way to do it in code?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > "Richard Grant" <fractal@clark.net> wrote in message news:bdn8nm$nr2$1@digitaldaemon.com...
> > > > > > > In article <bdlqba$2enr$1@digitaldaemon.com>, Matthew Wilson
> > says...
> > > > > > >
> > > > > > > >Is there a way to specify to the compiler to suppress certain
> > > > warnings?
> > > > > > >
> > > > > > > -w[errno]
> > > > > > >
> > > > > > > like -w18
> > > > > > >
> > > > > > > Richard
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>