Re: how to let gcc warn me when I use = in conditions
- From: Alan Balmer <albalmer@xxxxxxx>
- Date: Mon, 27 Jun 2005 12:07:54 -0700
On Mon, 27 Jun 2005 16:21:38 GMT, gazelle@xxxxxxxxxxxxxxxxxxx (Kenny
McCormack) wrote:
>In article <j680c1hu1m3tjrmd5tnd8j7lnhsf9u08e7@xxxxxxx>,
>Alan Balmer <albalmer@xxxxxxxxxxx> wrote:
>...
>>>If we carry this reasoning to the extreme the
>>>compiler should execute:
>>>
>>> fprintf(stderr, "WARNING \"%s\" may be invalid\n",
>>> current_token);
>>>
>>>after each lexical extraction from the source! :-) I envision
>>>marketing difficulties.
>>
>>Nonsense. Issuing a warning for all cases, as many (most?) compilers
>>can be asked to do, is no more likely to lead to this than your notion
>>of issuing the warning for only some cases.
>
>Whoosh!
Not exactly, but jokes don't improve the notion, either, and the
attempted distraction is temporary - he'll be making the same old
suggestion, followed by the same old argument, again soon.
--
Al Balmer
Balmer Consulting
removebalmerconsultingthis@xxxxxxx
.
- References:
- how to let gcc warn me when I use = in conditions
- From: PengYu.UT@xxxxxxxxx
- Re: how to let gcc warn me when I use = in conditions
- From: Alan Balmer
- Re: how to let gcc warn me when I use = in conditions
- From: CBFalconer
- Re: how to let gcc warn me when I use = in conditions
- From: Alan Balmer
- Re: how to let gcc warn me when I use = in conditions
- From: Kenny McCormack
- how to let gcc warn me when I use = in conditions
- Prev by Date: Re: Tool to trace function calls
- Next by Date: Re: About c++
- Previous by thread: Re: how to let gcc warn me when I use = in conditions
- Next by thread: Re: how to let gcc warn me when I use = in conditions
- Index(es):
Relevant Pages
|
|