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 `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 the same way > you'd > use `unsafe_wrap` on Julia 0.5. > > `@compat` is necessary only for more complicated cases where there's a > reason > why you can't make it just an ordinary function call. > > To sum up, to get rid of deprecation warnings write your code in the new > syntax. Add `@compat` only when Compat.jl's README tells you to do so. > > --Tim > > On Monday, August 29, 2016 8:46:42 AM CDT J Luis wrote: > > 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 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 29, 2016 at 6:11:19 AM UTC-7, J Luis wrote: > > >>> 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, what do you mean by this? If I don't use @compat (which I tried) > I > > >> get tons of deprecation messages. > > >
