Re: [julia-users] Re: Best practices for migrating 0.3 code to 0.4? (specifically constructors)

2015-03-14 Thread Ian Watson
I am seeing what looks like a similar problem trying to use PyPlot in version 0.4. When I issue 'using PyPlot', I get ERROR: LoadError: LoadError: LoadError: MethodError: `convert` has no method matching convert(::Type{Ptr{UInt8}}, ::ASCIIString) This may have arisen from a call to the

Re: [julia-users] Re: Best practices for migrating 0.3 code to 0.4? (specifically constructors)

2015-03-13 Thread René Donner
That string does represent a filename, doesn't it? Do you obtain that by calling readdir() at some point perhaps? This can now return a Array{Union(UTF8String,ASCIIString),1}, which I believe was not the case in 0.3. (At least I had to adapt my code at some point to deal with this) Am

[julia-users] Re: Best practices for migrating 0.3 code to 0.4? (specifically constructors)

2015-03-13 Thread Phil Tomson
On Thursday, March 12, 2015 at 9:00:45 PM UTC-7, Avik Sengupta wrote: I think this is simply due to your passing a UTF8String, while your function defined only for ASCIIString. Since there is no function defined for UTF8String, julia falls back to the default constructor that calls

[julia-users] Re: Best practices for migrating 0.3 code to 0.4? (specifically constructors)

2015-03-12 Thread Avik Sengupta
I think this is simply due to your passing a UTF8String, while your function defined only for ASCIIString. Since there is no function defined for UTF8String, julia falls back to the default constructor that calls convert. julia type A a::ASCIIString b::Int end julia