Thread overview
-v for error only
Jun 19, 2018
DigitalDesigns
Jun 19, 2018
Nicholas Wilson
Jun 19, 2018
DigitalDesigns
June 19, 2018
There needs to be a switch, if their isn't one already, where only errors are verbose.

When I use the -v switch it not only expands the error trace like it should but also adds all kinds of additional meaningless info(semantic3, module list, etc). All this additional information is generally useless and obscures the main point of using -v which is to get a deeper error trace.

When doing a lot of compile time work and using pragma msg, it can make things worse.

It would be nice if there was something in between the two extremes: Only shows longer error traces and only most important compiler verbosity. Better yet, implement a verbosity level -v1, ..., -v9 give 9 zones and one can enable any number of zones -v158 enables the errors for zones 1 5 and 8. Could use hex for more zones: -v14aef.

Anyways, I guess it's more of a dream feature...



June 19, 2018
On Tuesday, 19 June 2018 at 08:40:03 UTC, DigitalDesigns wrote:
> There needs to be a switch, if their isn't one already, where only errors are verbose.
>
> When I use the -v switch it not only expands the error trace like it should but also adds all kinds of additional meaningless info(semantic3, module list, etc). All this additional information is generally useless and obscures the main point of using -v which is to get a deeper error trace.
>
> When doing a lot of compile time work and using pragma msg, it can make things worse.
>
> It would be nice if there was something in between the two extremes: Only shows longer error traces and only most important compiler verbosity. Better yet, implement a verbosity level -v1, ..., -v9 give 9 zones and one can enable any number of zones -v158 enables the errors for zones 1 5 and 8. Could use hex for more zones: -v14aef.
>
> Anyways, I guess it's more of a dream feature...

The info is not useless, it very useful when debugging the compiler :)

What additional info do you get with -v that helps?
(I ask having only really used LDC's -vv for debugging it (which produces waaaay more output than DMD))

June 19, 2018
On Tuesday, 19 June 2018 at 12:44:26 UTC, Nicholas Wilson wrote:
> On Tuesday, 19 June 2018 at 08:40:03 UTC, DigitalDesigns wrote:
>> There needs to be a switch, if their isn't one already, where only errors are verbose.
>>
>> When I use the -v switch it not only expands the error trace like it should but also adds all kinds of additional meaningless info(semantic3, module list, etc). All this additional information is generally useless and obscures the main point of using -v which is to get a deeper error trace.
>>
>> When doing a lot of compile time work and using pragma msg, it can make things worse.
>>
>> It would be nice if there was something in between the two extremes: Only shows longer error traces and only most important compiler verbosity. Better yet, implement a verbosity level -v1, ..., -v9 give 9 zones and one can enable any number of zones -v158 enables the errors for zones 1 5 and 8. Could use hex for more zones: -v14aef.
>>
>> Anyways, I guess it's more of a dream feature...
>
> The info is not useless, it very useful when debugging the compiler :)
>
> What additional info do you get with -v that helps?
> (I ask having only really used LDC's -vv for debugging it (which produces waaaay more output than DMD))

It may or may not be helpful. Just because it can show a lot of shit doesn't mean it should because it is not always helpful under all circumstances.