[OT] OT: Null checks.
Sebastiaan Koppe
mail at skoppe.eu
Sun May 4 06:55:02 UTC 2025
On Sunday, 4 May 2025 at 06:18:28 UTC, Richard (Rikki) Andrew
Cattermole wrote:
> On 04/05/2025 5:40 PM, Timon Gehr wrote:
>> The whole: "We really need to make sure people cannot get any
>> information out of a failing process unless they run the
>> program from the command line and then we need to make sure
>> nothing but a stack trace will escape unless we are running in
>> a debugger" is simply not workable. I don't understand what
>> you are chasing in this instance, but it is not utility. It
>> almost seems like your only experience with remote crashes is
>> those that happen frequently and repeatably, and within a
>> terminal.
>
> This may be where you need to emphasize that you are talking
> from a users perspective, not a language developer.
>
> Based upon your other comments, its resulting in some severe
> problems for you.
Of course the problem isn't unique to Timon; it hits everybody
doing anything remotely usable.
It is the equivalent of a program crashing and showing an
unhelpful dialog saying: "The program crashed.". The response is
an universal one, along the lines of "Thank you for telling me
that, it didn't occur to me."
The minimum acceptable response is a dialog with opt-out sending
of crash report. For CLI programs you have more leeway though.
More information about the Digitalmars-d
mailing list