-
Notifications
You must be signed in to change notification settings - Fork 6
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
Line number logging with __LINE__ doesn't work #1
Comments
For reference, I copped out by just requiring the line number as an input to the macro; see here |
Ah, that's a pity! Thanks for the xref :-) @ihnorton has a scary looking hack that gives better results here but it still doesn't do quite the right thing. |
Another related issue JuliaLang/julia#9577 |
This is solved in 0.7 thanks to JuliaLang/julia#21746 There is no, and will be no solution to this before 0.7 is released, by the looks of things. |
Related PR to make this easier with Jameson's new code in 0.7 - JuliaLang/julia#22623 |
As pointed out by @quinnj,
@__LINE__
doesn't do what a C programmer naively expects :-/f6db371#commitcomment-20846418
This could come from a backtrace instead, it just seems a bit excessive to invoke one to get something that could/should be inlined at the call site.
The text was updated successfully, but these errors were encountered: