Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Format of error messages #6987

Closed
PhilippeMaincon opened this issue May 27, 2014 · 5 comments
Closed

Format of error messages #6987

PhilippeMaincon opened this issue May 27, 2014 · 5 comments

Comments

@PhilippeMaincon
Copy link

Hi everyone,
I'm using Julia studio 0.4.4 with Julia 0.3.0. Being human, I write bugs. I get error messages like

LoadError("U:/prosjekt/Materialer_og_nanoteknologi/MK102003050_Arctic Materials II/Fag/WP3_Safety Criteria for Steels PN102003050-4/T36_Simlified tool/Linespring in Abaqus/ls.jl",145,ErrorException("argument dimensions do not match"))

So my remarks:

  1. "LoadError" is cryptic.
  2. The (huge) file path deserves an own line, so that I can see the error type without paning the window.
  3. The line number 145 refers to the line in the top script, where I have a function call, and I am left to search which line in which subfunction throws the error.

I mention this to emphasize that this desrve priority. But if someone out there can show me a workaround, I will be very thankfull. (NB: I tried the Debug package, but did not get it to stop in the code. No clue what I did wrong. Is it usable - I am just a bit slow - or is too early in the development curve).

Julia is great, keep it up.

Philippe

@ivarne
Copy link
Sponsor Member

ivarne commented May 27, 2014

Somewhat cryptic error messages are definitely a sore point in Julia. Line numbers does not always point to the exact line of the error, but to the beginning of the enclosing block. There are different ideas floating around to improve the situation, but there are also different opinions about what is really needed.

When it comes to the specific printing of the LoadError, I think that is related to the way Julia Studio works, because I usually get a much more pretty error message, with the ErrorException on top, with a backtrace and while loading $(e.file), in expression starting on line $(e.line)" at the bottom. You might consider opening an issue with them.

PS: Great to see that there are Julia users at SINTEF in Trondheim!

@PhilippeMaincon
Copy link
Author

Takk Ivar!
So far, I do not know of other colleagues trying Julia out, but I am spreading the word.
If you do not use JuliaStudio, what do you use? emacs? (I come from a pampered life in Matlab!)

Vi snakkes

Philippe

@ivarne
Copy link
Sponsor Member

ivarne commented May 27, 2014

I use a text editor (vim and Textmate) and the command line on a Mac computer. Lots of people also use iJulia where you use the browser to edit and execute code.

@PhilippeMaincon
Copy link
Author

Thanks, I'll have a look at these.

@JeffBezanson
Copy link
Sponsor Member

This can be discussed in #4744. Ivar is also correct that we (IJulia or standard REPL) don't normally print errors that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants