Many thanks for the feedback. I'm sure this isn't easy and I'm looking forward to any progress made there.
On Sunday, May 4, 2014 5:28:50 PM UTC-7, Tim Holy wrote: > > In addition to what Tony said, most errors that are not parser errors > _should_ > give you useful line numbers. One some platforms the backtraces have been > problematic, but one of the long-term offenders is at the threshold of > being > fixed (https://github.com/JuliaLang/julia/issues/3469) and Isaiah has > done some > good work with the other major one (can't find the issue right now). > > Best, > --Tim > > On Sunday, May 04, 2014 11:41:57 AM Dominique Orban wrote: > > I'm finding error messages and warnings emitted by Julia quite opaque, > > making development difficult. For instance, I tried translating a > function > > from Matlab code by copy-pasting and changing a few things here and > there, > > but Julia tells me things such as "ERROR: arrays could not be broadcast > to > > a common size" or "ERROR: syntax: unexpected ,", usually without any > line > > number as a clue. When it does give a line number, it corresponds to the > > function declaration and that doesn't help. Are there any plans to > improve > > the error reporting? >
