4 ms·
Meanwhile, for as long as I can remember, Visual Studio could easily jump straight to the offending null variable when debugging C#.
by jimmaswell 8y ago
Meanwhile, for as long as I can remember, Visual Studio could easily jump straight to the offending null variable when debugging C#.
- zahrc 8y agoThere’s a difference between an IDE offering it, or the JDK
- Gibbon1 8y agoThe CLR gives you all that information. It's not just an IDE thing.
- peteri 8y agoStill an open issue https://github.com/dotnet/coreclr/issues/25 https://github.com/dotnet/coreclr/issues/25 The debugger in VS2017 does give the information, but I suspect thats just by re-evaluating the expression.
- deleted 8y ago[deleted]
- Gibbon1 8y agoI seem to remember that too, null pointer exception coughs up more than enough information to figure out where it barfed. Makes me feel that complaints about null aren't really about null itself but languages and OS's not generating useful error messages.