On 25/09/2013 17:45, Sean Kelly wrote:
On Sep 24, 2013, at 11:14 PM, Walter Bright <[email protected]> wrote:
On 9/24/2013 10:54 PM, "Luís Marques" <[email protected]>" wrote:
- Based on my experience with javac and clang, providing a caret (and ranges
around the offending expressions, as in clang) is very useful *to me*, and I
would be very pleased to see them on the D compilers, even if that information
was not present in the debugger, so as not to regress compiler performance.
Thank you for a very reasonable reply.
Yeah, I've never cared about having this information in the debugger. Only at
compile time.
What does it even mean to have column/source-range information for
errors in the debugger?? There is no notion of language errors or
warnings in the debugger in the first place. Unless you mean for an
expression evaluator (a pretty advanced feature)?
--
Bruno Medeiros - Software Engineer
