erm... yes. sorry that was a stupid question.
thanks anyway!
On Monday, 19 September 2016 10:48:44 UTC+2, Bart Janssens wrote:
>
>
>
> On Mon, Sep 19, 2016 at 10:11 AM Florian Oswald > wrote:
>
>>
>> So I read somewhere that my construction involving `eval` is bad
>> practice. can anyone give m
On Mon, Sep 19, 2016 at 10:11 AM Florian Oswald
wrote:
>
> So I read somewhere that my construction involving `eval` is bad practice.
> can anyone give me some guidance as to what is the proper julian way of
> expressing this:
>
> eval(Expr(:call,f,3))?
>
>
Just calling the function:
f(3)
?
Oh, I see!
So I read somewhere that my construction involving `eval` is bad practice.
can anyone give me some guidance as to what is the proper julian way of
expressing this:
eval(Expr(:call,f,3))?
thanks!
On Monday, 19 September 2016 09:46:55 UTC+2, Bart Janssens wrote:
>
> In 0.5-rc4 your
In 0.5-rc4 your code runs without any warnings. I think only the call
function was deprecated, not the :call symbol in an expression tree:
dump(:(f(3))) yields:
Expr
head: Symbol call
args: Array{Any}((2,))
1: Symbol f
2: Int64 3
typ: Any
Cheers,
Bart
On Mon, Sep 19, 2016 at 9:32 A
i was trying to make sense of the final outcome of the discussion
here https://github.com/JuliaLang/julia/pull/13412, but no way. Also I'm
not sure what to search for in the documentation (?Base.call tells me it's
deprecated.)
So:
if up to now I programmatically evaluate a function f like tha
