Why the hell do exceptions give error in the library rather than the user code?
Jonathan Marler
johnnymarler at gmail.com
Fri Sep 14 15:40:46 UTC 2018
On Friday, 14 September 2018 at 14:34:36 UTC, Josphe Brigmo wrote:
> std.file.FileException at C:\D\dmd2\windows\bin\..\..\src\phobos\std\file.d(3153):
>
> It is very annoying when the only error info I have is pointing
> to code in a library which tells me absolutely nothing about
> where the error occurs in the in the user code(which is what
> matters).
>
>
> Surely the call stack can be unrolled to find code that exists
> in the user code? Or at least display several lines like a
> trace stack.
Not getting a stack trace? What platform are you on and what's
the command line you used to compile?
More information about the Digitalmars-d
mailing list