On 20/02/2021 16:46, David Malcolm wrote:
> On Sat, 2021-02-20 at 15:25 +0100, David Brown wrote:
>
> I think we need to think about both of these use-cases e.g. as we
> implement our diagnostics, and that we should mention this distinction
> in our UX guidelines...
>
>> Is it possible to distinguish these uses, and then have different
>> default flags? Perhaps something as simple as looking at the name
>> used
>> to call the compiler - "cc" or "gcc" ?
>>
>
> ...but I'm wary of having an actual distinction between them in the
> code; it seems like a way to complicate things and lead to "weird"
> build failures.
>
Fair enough.
> Thought experiment: what might a "--this-is-my-code" option do?
>
It should read the programmer's mind and tell them of any discrepancies
between what they wrote and what they meant :-)
I'd say it should make "-Wall" the default, and complain if "-std" is
not specified explicitly, and if there is no "-O" flag (or a #pragma GCC
optimise early in the code - even if it is an explicit -O0). That would
cover things that I see people getting wrong regularly.
(I am a big fan of explicit rather than implicit, and having default
behaviour be a complaint that you are relying on default behaviour. But
I may not be a typical user.)
> Hope this is constructive
> Dave
>
