3 ms·
I've been trying out Julia for a couple weeks. I love the language, it's simple, powerful, and fast. My problem is that I've run into a lot of cases where I hav
by DennisP 13y ago
I've been trying out Julia for a couple weeks. I love the language, it's simple, powerful, and fast. My problem is that I've run into a lot of cases where I have an error, but no indication of where the error is. Sometimes it's a syntax error somewhere in the file, other times it's a stack trace that gives me my top-level function call and a line somewhere in the standard library, but nothing in between.
So I'm finding I can write the code very quickly, but if I get an error like this I lose all the time I gained and more. I'm sure this is a matter of it being such a young language, and also that someone more experienced would avoid many of the pitfalls catching me. But for noobs like me it's difficult. I hope they improve this soon.
- thearn4 13y agoI've been playing around with Julia for about a week now too. There are so many things to like, but I agree - the tracebacks are pretty useless half of the time.
- green7ea 13y agoThe error messages are driving me nuts as well. Otherwise, Julia is a very impressive language that can do more than replace Matlab. The only other irk I have is that an ASCIIString doesn't have UTF8String as a parent type (ASCIIString <: UTF8String -> false)
- StefanKarpinski 13y agoWhich version of Julia are you using and on what platform? Windows backtraces are pretty bad, but other platforms decent. The situation on Windows is likely to improve soon, fortunately. If you have specific problems that are reproducible, it would be great to have bug reports so we can improve things: https://github.com/JuliaLang/julia/issues https://github.com/JuliaLang/julia/issues.
- DennisP 13y agoVersion 0.2.0 on Ubuntu. I should have kept better notes. Going forward, I'll try and reproduce in small amounts of code and file reports. One was pretty silly, I used "end" as a variable name. It blew up with a syntax error on a line where I was assigning to it, but didn't tell me what line or what variable name. (But it did say something about an unexpected assignment, so it knew where the problem was, it just didn't tell me.) I've got the stacktrace issue right now with an error regarding an incorrect byte index into a unicode string. I get why that happens, just can't find what's causing it in my code. Edit: changed to an ascii string after seeing someone mention it here, now I'm getting a BoundsError in copy! at array.jl:49, and again the stacktrace tells me nothing else besides the top-level function call.