-
Notifications
You must be signed in to change notification settings - Fork 13
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
Using @debug function func(x) results in ERROR: T not defined #65
Comments
No, that's not supposed to happen. Is this on Julia 0.4? Version 0.4 is very much in flux right now, so I haven't tried to upgrade the package to support it yet. Can you try with a 0.3 version? |
It is Julia 0.4 I will try it in 0.3, but my ppa's got set to dev version Don On Tue, Oct 28, 2014 at 1:38 PM, toivoh [email protected] wrote:
|
Works ok in 0.3.2 Is there a place where the schedule for 0.4 is Don On Tue, Oct 28, 2014 at 2:25 PM, Don MacMillen [email protected] wrote:
|
Having the same problem on Windows using Julia 0.4 (2014-12-23). I can't switch back to 0.3 as I need some new functions. Would love to see this fixed :) |
I've opened the issue JuliaLang/julia#10445 about the above error. We'll see how it plays out. |
Not sure how to fix the concatenation deprecations, though. As far as I can tell, the code is not concatenating anything, just using `[a, b]` syntax to construct vectors from elements. Not sure how to fix the deprecation for `Dict` syntax either, as the new syntax is invalid in Julia 0.3.
Closed by ebb4cc0. Debug now seems to work on Julia 0.4. |
Ubuntu 14.04
Version 0.4.0-dev+1330 (2014-10-28 03:56 UTC)
Commit 7fdc860* (0 days old master)
x86_64-linux-gnu
julia> using Debug
WARNING: deprecated syntax "{a for a in b}" at /home/ubuntu/.julia/v0.4/Debug/src/Analysis.jl:40.
Use "Any[a for a in b]" instead.
... and more deprecated syntax warnings (this is not the problem)
...
... this is the problem
julia> @debug function square(x)
return x*x
end
ERROR: T not defined
julia>
Doesn't seem like a usage error.
The text was updated successfully, but these errors were encountered: