Re: [julia-users] Re: Hard time with Compat and 0.5

2016-08-29 Thread J Luis
Ah, I got it now. Thanks. segunda-feira, 29 de Agosto de 2016 às 17:05:58 UTC+1, Tim Holy escreveu: > > To rephrase what Steven and Tony said, for some things you won't need a > macro. > For example, `unsafe_wrap` didn't exist on Julia 0.4, but Compat contains > an > implementation of

Re: [julia-users] Re: Hard time with Compat and 0.5

2016-08-29 Thread Tim Holy
To rephrase what Steven and Tony said, for some things you won't need a macro. For example, `unsafe_wrap` didn't exist on Julia 0.4, but Compat contains an implementation of `unsafe_wrap` for use on Julia 0.4. It's just a plain-old function call, so you don't need `@compat`---just use it in

[julia-users] Re: Hard time with Compat and 0.5

2016-08-29 Thread J Luis
Ok, but than how do I quiet the tons of deprecation messages that show up? segunda-feira, 29 de Agosto de 2016 às 15:57:34 UTC+1, Tony Kelman escreveu: > > You generally only need to call the @compat macro when you're trying to > use some new syntax that didn't parse correctly on older versions

[julia-users] Re: Hard time with Compat and 0.5

2016-08-29 Thread Tony Kelman
You generally only need to call the @compat macro when you're trying to use some new syntax that didn't parse correctly on older versions of Julia. If it parses correctly, Compat usually implements it with normal functions and methods, no need for a syntax-rewriting macro. On Monday, August

[julia-users] Re: Hard time with Compat and 0.5

2016-08-29 Thread J Luis
> > No, it is: > > t = unsafe_wrap(Array, Gb.data, h.size) > > as in the deprecation warning. > Thanks (I'd figured it out too meanwhile) > (You don't need @compat just for function calls. You only need @compat > for things where the syntax changes in a more complicated way.) > Hmm,

[julia-users] Re: Hard time with Compat and 0.5

2016-08-27 Thread Steven G. Johnson
On Friday, August 26, 2016 at 9:15:23 PM UTC-4, J Luis wrote: > > Hi, > So I started trying to port my code to 0.5 using Compat and it seams a > hell is expecting me. > This is one example of what happens when I try to follow the deprecation > suggestions. This > > t =

[julia-users] Re: Hard time with Compat and 0.5

2016-08-27 Thread DNF
In the first one you are passing in [X.name...] while in the other one you are passing in X.name. Could you not just write: name = String([X.name...]) On Saturday, August 27, 2016 at 3:29:32 AM UTC+2, J Luis wrote: > > Ok, I figured that one (Really needed a first argument 'Array') > > But

[julia-users] Re: Hard time with Compat and 0.5

2016-08-26 Thread J Luis
Ok, I figured that one (Really needed a first argument 'Array') But now this @show(typeof(X.name)) name = bytestring([X.name...]) typeof(X.name) = Tuple{UInt8,UInt8,UInt8,UInt8,UInt8,UInt8,UInt8,UInt8,UInt8 ,UInt8,UInt8,UInt8,UInt8,UInt8,UInt8,UInt8} WARNING: bytestring(v::Vector{UInt8}) is