popov wrote:
> Note: It is a good practice to turn on all warnings (-Wall) for the gcc

Actually, it is not.  It generates plenty of completely bogus warnings. 
Only inexperienced people compile with all warnings enabled.

	Thorsten

Post a reply to this message

popov wrote:
> No I mean:
> 
> Did you try: ./configure CXXFLAGS="-Wal" COMPILED_BY="me"
> 
> On my system (OSX 10.3.5, ) I get: "C++ compiler cannot create executables"
> 
> What do you get?

Probably the same, though I cannot try on the system I am currently writing 
this on.

	Thorsten

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> popov wrote:
> > Note: It is a good practice to turn on all warnings (-Wall) for the gcc
>
> Actually, it is not.  It generates plenty of completely bogus warnings.
> Only inexperienced people compile with all warnings enabled.
>
>  Thorsten

> Actually, it is not.  It generates plenty of completely bogus warnings.
> Only inexperienced people compile with all warnings enabled.

This is really plain wrong!

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> popov wrote:
> > No I mean:
> >
> > Did you try: ./configure CXXFLAGS="-Wal" COMPILED_BY="me"
> >
> > On my system (OSX 10.3.5, ) I get: "C++ compiler cannot create executables"
> >
> > What do you get?
>
> Probably the same, though I cannot try on the system I am currently writing
> this on.
>
>  Thorsten

> Probably the same, though I cannot try on the system I am currently writing
> this on.

If it is the same (and I thinck it will be) what was so 'plain wrong' on my
post?
(beside the fact the users problem was already solved)

Post a reply to this message

popov wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
> 
>>popov wrote:
>>
>>>No I mean:
>>>
>>>Did you try: ./configure CXXFLAGS="-Wal" COMPILED_BY="me"
>>>
>>>On my system (OSX 10.3.5, ) I get: "C++ compiler cannot create executables"
>>>
>>>What do you get?
>>
>>Probably the same, though I cannot try on the system I am currently writing
>>this on.
>>
>> Thorsten
> 
> 
>>Probably the same, though I cannot try on the system I am currently writing
>>this on.
> 
> 
> If it is the same (and I thinck it will be) what was so 'plain wrong' on my
> post?
> (beside the fact the users problem was already solved)

Suggesting that it is a wrong command-line while the problem was a missing 
compiler.  That also happens to be the most likely cause as the development 
tools are not installed by default.

	Thorsten

Post a reply to this message

popov wrote:
>>Actually, it is not.  It generates plenty of completely bogus warnings.
>>Only inexperienced people compile with all warnings enabled.
> 
> This is really plain wrong!

No, it just shows you have no experience with advanced C++ and using 
multiple compilers to compile the same source code.

	Thorsten

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> popov wrote:
> >>Actually, it is not.  It generates plenty of completely bogus warnings.
> >>Only inexperienced people compile with all warnings enabled.
> >
> > This is really plain wrong!
>
> No, it just shows you have no experience with advanced C++ and using
> multiple compilers to compile the same source code.
>
>  Thorsten

So you suggest not to turn warnings on?
This means not to realize them. Most warnings are indeed just warnings (and
some might be bogus). However there might be warnings indicating some
really serious problem. Your code may run but the results may not be
correct.

And sometimes it happens that compiler A does not realize the problem but
compiler B does realize it. Compiling with different compilers and looking
to all warnings is some kind of quality assurance.

But wait, why do I tell this. You have so much experience...

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> popov wrote:
> > Thorsten Froehlich <tho### [at] trfde> wrote:
> >
> >>popov wrote:
> >>
> >>>No I mean:
> >>>
> >>>Did you try: ./configure CXXFLAGS="-Wal" COMPILED_BY="me"
> >>>
> >>>On my system (OSX 10.3.5, ) I get: "C++ compiler cannot create executables"
> >>>
> >>>What do you get?
> >>
> >>Probably the same, though I cannot try on the system I am currently writing
> >>this on.
> >>
> >> Thorsten
> >
> >
> >>Probably the same, though I cannot try on the system I am currently writing
> >>this on.
> >
> >
> > If it is the same (and I thinck it will be) what was so 'plain wrong' on my
> > post?
> > (beside the fact the users problem was already solved)
>
> Suggesting that it is a wrong command-line while the problem was a missing
> compiler.  That also happens to be the most likely cause as the development
> tools are not installed by default.
>
>  Thorsten

I thought this info could be of interest for those who have the compiler
installed but get this error. Ok, slightly out of topic but not out of
context and probably not plain wrong.

Post a reply to this message

popov wrote:
> So you suggest not to turn warnings on?

When did you get that idea?  You certainly know that there is more than just 
a warning on/off switch in every compiler out there.  So how to conclude 
from saying that not all warnings should be on by default that all warnings 
should be off is a rather strange interpretation...

 > But wait, why do I tell this. You have so much experience...

Good question!

	Thorsten

Post a reply to this message

popov wrote:
> And sometimes it happens that compiler A does not realize the problem but
> compiler B does realize it. Compiling with different compilers and looking
> to all warnings is some kind of quality assurance.

If you have to rely on warnings to do your quality assurance you are in 
really serious trouble!!!  You also happen to make a very academic argument, 
as the "benefit" you present happens to be the biggest problem: It is 
possible, and does actually happen, that code "fixing" a warning on one 
compiler causes one on another.  Not to mention that code commonly 
introduced to "fix" compiler warnings does a whole lot of harm, in 
particular when done in the form of C-style casts.  And in other cases the 
warning cannot be eliminating without code duplication, which you would have 
noticed when compiling reasonably complex template code and getting tons of 
unused variable or argument warnings...

	Thorsten

Post a reply to this message