-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Comments
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 PS: Great to see that there are Julia users at SINTEF in Trondheim! |
Takk Ivar! Vi snakkes Philippe |
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. |
Thanks, I'll have a look at these. |
This can be discussed in #4744. Ivar is also correct that we (IJulia or standard REPL) don't normally print errors that way. |
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:
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
The text was updated successfully, but these errors were encountered: