[Info-vax] Why so much Unix envy?

[Shark8]

On 03-Sep-14 07:06, bill at server3.cs.scranton.edu (Bill Gunshannon) wrote:
> In article <y%oNv.72081$JH1.18826 at fx08.iad>,
> 	Shark8 <OneWingedShark at gmail.com> writes:
>> On 02-Sep-14 07:27, bill at server3.cs.scranton.edu (Bill Gunshannon) wrote:
>>> You can do wonders with cleaning up C code now by looking at the warnings
>>> and fixing what they warn you about.  Instead, most programmers just turn
>>> off all the warnings to get a "clean" compile.
>>
>> Which means that the warnings are, generally, useless.
>
> Why would that mean the warnings are useless?

Because they're being ignored.

> The warnings carry meaning.

And how is that meaning of *any* value if they "turn off all the 
warnings to get a 'clean' compile"?

> It is the useless programmer who chooses to ignore them rather than fix
> what they are warning about.  Or are you arguing that the option to turn
> them off should be removed from the compiler?

IMO, many things that are warnings [in C] ought to be errors -- but then 
C has more of a "let anything compile" philosophy than many other languages.