See also #7732 https://github.com/JuliaLang/julia/issues/7732
I'm not sure why this is not getting traction. It seems like a useful
feature to me, but it probably doesn't seem to add much value, and it has
impact on the correctness of high performance Julia libraries. It should
probably be
Also check out Logging.jl, which does have macros for enabling/disabling
printing/logging at different levels.
Kevin
On Tue, Aug 19, 2014 at 3:09 AM, Ivar Nesje iva...@gmail.com wrote:
See also #7732 https://github.com/JuliaLang/julia/issues/7732
I'm not sure why this is not getting
On Tuesday, August 19, 2014 12:11:49 PM UTC+2, Kevin Squire wrote:
Also check out Logging.jl, which does have macros for enabling/disabling
printing/logging at different levels.
Thank you for point out Logging.jl, it seems to do what I was looking for.
Jan
Is there a way for a user that downloads the RC4 binary to run the test
suit? That would be a good way to help uncover those pesky bugs.
On Monday, August 18, 2014 6:36:47 PM UTC+3, Stefan Karpinski wrote:
+1,000,000
On Mon, Aug 18, 2014 at 11:25 AM, John Myles White johnmyl...@gmail.com
Hi Julia users,
I was trying to convert an array of char's to string, and I've noticed
functions such as string or CharString, but non of these seem to work for
my case:
Julia console:
==
julia a = ['a', 'b', 'c']
3-element Array{Char,1}:
'a'
'b'
'c'
julia string(a)
Try join()
On Tue, Aug 19, 2014 at 8:04 AM, Ning Yin yin@gmail.com wrote:
Hi Julia users,
I was trying to convert an array of char's to string, and I've noticed
functions such as string or CharString, but non of these seem to work for
my case:
Julia console:
==
julia a
jl_uv_dlopen was added 2 weeks ago and is now used by BinDeps, so older
Julia installs are breaking.
Installing 0.3.0-rc4 fixes the issue.
Just in case anyone else runs into the issue.
peace,
s
hey!
yeah no worries! when I overcame my impatience (which led me to abort the
download after 2 seconds because of the wrong name), I found out that the
package had the correct content.
cheers
On 19 August 2014 16:54, Elliot Saba staticfl...@gmail.com wrote:
Whoops, sorry about that Florian!
I don't think this is possible. This sounds like a case where PDMats needs a
new release. You can implement a release yourself, make a pull request to
METADATA and ask Dahua for permission to merge it.
-- John
On Aug 19, 2014, at 10:13 AM, Spencer Lyon spencerly...@gmail.com wrote:
Is there
That's what I thought. I'm happy to do that
To do this I just need to do
`Pkg.tag(PDMats)`
Then push that commit to my fork of METADATA and submit a PR, right?
On Tuesday, August 19, 2014 10:13:06 AM UTC-7, Spencer Lyon wrote:
Is there a way to specify that a package depends on the current
That should work. :)
-- Leah
On Tue, Aug 19, 2014 at 12:28 PM, Spencer Lyon spencerly...@gmail.com
wrote:
That's what I thought. I'm happy to do that
To do this I just need to do
`Pkg.tag(PDMats)`
Then push that commit to my fork of METADATA and submit a PR, right?
On Tuesday, August
On Tuesday, August 19, 2014 11:09:21 AM UTC-4, g wrote:
You could try adapting this python stack overflow answer. I've only ever
done it with qt4 and the matplotlib api from python, but it is certainly
possible.
This is a really cool family of tricks. Time for me to start replacing some
::Function specifiers in my argument lists...
I saw in julia base that `Base.Callable`, an alias for Union(Function,
DataType), is used in argument lists.
I'm starting to consider replacing most normal functions by
Done: https://github.com/JuliaLang/METADATA.jl/pull/1273
Thanks guys
On Tuesday, August 19, 2014 10:58:46 AM UTC-7, Leah Hanson wrote:
That should work. :)
-- Leah
On Tue, Aug 19, 2014 at 12:28 PM, Spencer Lyon spence...@gmail.com
javascript: wrote:
That's what I thought. I'm happy to
Suppose I am defining a function that operates on any two real numbers.
Which of the following ways of specifying types is preferred (in terms of
idomatic Julia and performance considerations) and why?
```julia
function foo1(x::Real, y::Real) = ...
function foo2{ T: Real}(x::T, y::T) = ...
function foo4(x,y)
is also a valid way that allows most flexibility. From a performance point
of view all functions are equally fast.
Specifying types is not done for performance reasons but to allow for
dispatching on the type. foo2 and foo3 are of course semantically different
because foo2
Performance wise it makes no difference. The JIT will produce the same code
for all three:
foo1(x::Real, y::Real) = x + y
foo2{ T: Real}(x::T, y::T) = x + y
foo3{T : Real, S : Real}(x::T, y::S) = x + y
You can verify it by running @code_native on all of them. They will all
result in the same
(Posted earlier in IRC, but I'm told this is considerably more active.)
So in the recent past (a few weeks ago), on 0.2 on Ubuntu trusty, I could
pre-install the binary dependencies of ICU, HttpParser, Nettle, ZMQ, etc.
and the Julia package install would proceed smoothly without trying to
Hi Spencer,
yes the ScalarOrArray type will work and be fast. In that case you could
have also not specified the types at all.
We call this duck typing which is a term that comes from the python world.
I think there is no preferred way to do this in Julia and there are
people that favor the
Hi all,
I think this is a typically asked question, but I don't know whether it is
possible now in julia v0.3.
Namely to make the up/down arrows search completion history in the REPL. If
so, I will be happy to document it in the docs in the FAQ section.
Thanks.
I couldn't find it via googling, but there is a page that documents this.
Although the documentation would benefit from descriptions of how to use
these shortcuts in windowed terminals (eg shift page-up works in the OSX
terminal).
There is interest in this feature, but it hasn't been implemented
yet: https://github.com/JuliaLang/julia/issues/6377
Dear all,
Consider the following code:
try
require(ImageView)
global view = ImageView.view
catch err
@show err
# fallback to nothing
global view = view(args...; kargs...) = (nothing, nothing)
end
I have ImageView installed, but the catch block is executed with err =
OK This worked (after modifying by hand matplotlib/pyplot.py to change
plt.show(block=False) to plt.ion(), possibly updating matplotlib would work):
PyPlot.show()
for k=1:20
PyPlot.plot([1:10],1+k*[1:10])
PyPlot.draw()
PyPlot.pause(0.05)
end
On 20 Aug 2014, at 4:02 am, Steven G.
What happens if you use import instead is require?
On Tuesday, August 19, 2014, Júlio Hoffimann julio.hoffim...@gmail.com
wrote:
Dear all,
Consider the following code:
try
require(ImageView)
global view = ImageView.view
catch err
@show err
# fallback to nothing
You know about the Ctrl-r shortcut though, right?
--Tim
On Tuesday, August 19, 2014 10:57:19 PM Carlos Becker wrote:
Hi all,
I think this is a typically asked question, but I don't know whether it is
possible now in julia v0.3.
Namely to make the up/down arrows search completion history in
Thanks Tobi, that was exactly the type of response I was looking for.
On Tuesday, August 19, 2014 1:22:45 PM UTC-7, Tobias Knopp wrote:
Hi Spencer,
yes the ScalarOrArray type will work and be fast. In that case you could
have also not specified the types at all.
We call this duck typing
Hi Kevin,
What happens if you use import instead is require?
ERROR: error compiling anonymous: unsupported or misplaced expression
import in function anonymous
Júlio.
It’s a bit ugly, but this should work:
try
eval(Expr(:import, :ImageView))
global view = ImageView.view
catch err
@show err
# fallback to nothing
global view = view(args...; kargs...) = (nothing, nothing)
end
On Tuesday, August 19, 2014 9:00:39 PM UTC-4, Júlio Hoffimann
Hi Joey,
It’s a bit ugly, but this should work:
try
eval(Expr(:import, :ImageView))
global view = ImageView.view
catch err
@show err
# fallback to nothing
global view = view(args...; kargs...) = (nothing, nothing)
end
Unfortunately it doesn't work:
err =
Is there a way for a user that downloads the RC4 binary to run the test
suit? That would be a good way to help uncover those pesky bugs.
This question makes me happy. Thanks Ivar for answering it!
This may do what you want (snippet from JuMP):
if isdir(Pkg.dir(ArrayViews))
eval(Expr(:import,:ArrayViews))
const subarr = ArrayViews.view
else
const subarr = Base.sub
end
On Tuesday, August 19, 2014 7:38:27 PM UTC-6, Júlio Hoffimann wrote:
Hi Joey,
It’s a bit ugly, but this
As a newcomer to Julia, I'm having a bit of trouble following this
discussion: is it OK if I try to summarize it in my own words and you tell
me whether I've understood?
'Traditional' Julia: you can pass a function f as an argument to another
function g.
Rafael's functors: instead you create
Thanks! That worked.
I also found out that both string(a...) and CharString(a...) worked, though
I don't understand why the '...' is necessary here.
On Tuesday, August 19, 2014 9:50:33 PM UTC+8, Jacob Quinn wrote:
Try join()
On Tue, Aug 19, 2014 at 8:04 AM, Ning Yin yin...@gmail.com
That is the splice operator (also known as splat). It causes the contents
of `a` to be passed as indvidual arguments rather than passing `a` as an
array. So, string() behaves differently.
On Tue, Aug 19, 2014 at 11:55 PM, Ning Yin yin@gmail.com wrote:
Thanks! That worked.
I also found
We should really have a FAQ for this. This is something that tripped me up for
a while.
I’ll write up sometime.
— John
On Aug 19, 2014, at 9:11 PM, Isaiah Norton isaiah.nor...@gmail.com wrote:
That is the splice operator (also known as splat). It causes the contents
of `a` to be passed as
36 matches
Mail list logo
