[julia-users] Re: Dispatch on Vector{AbstractString} as an optional parameter

That's what I ended up doing but keyword arguments have the advantage of being self-documenting. Thanks for the explanations. On Friday, March 25, 2016 at 10:07:54 PM UTC-4, Greg Plowman wrote: > > Thanks Matt, that helps my understanding of keyword arguments. > > It also occurs to me that if

[julia-users] Re: Dispatch on Vector{AbstractString} as an optional parameter

Thanks Matt, that helps my understanding of keyword arguments. It also occurs to me that if you don't really require *keyword* arguments then you could define as: function g(s::AbstractString) println(s) end function g{S<:AbstractString}(s::AbstractString, v::Vector{S}) println(s)

[julia-users] Re: Dispatch on Vector{AbstractString} as an optional parameter

There's a few things going on here. First, you only define one method for `g` — your second definition overwrites the first because keyword arguments don't participate in multiple dispatch. There's been a warning added here in 0.5. So the one method you define just takes one argument and one

[julia-users] Dispatch on Vector{AbstractString} as an optional parameter

I (think I) understand the issue in this thread: https://groups.google.com/forum/#!searchin/julia-users/AbstractString/julia-users/HBMDbnRTH9g/cuqa6hB8AQAJ but I have the same problem with a keyword argument: function g(s :: AbstractString; v :: Vector{AbstractString}=AbstractString [])

RE: [julia-users] Determine the module where a type is declared

Perfect, thanks! > -Original Message- > From: julia-users@googlegroups.com [mailto:julia- > us...@googlegroups.com] On Behalf Of Yichao Yu > Sent: Friday, March 25, 2016 12:19 PM > To: Julia Users > Subject: Re: [julia-users] Determine the module where a

[julia-users] Re: update for julialang.org front page code ...

the docs appear to have this corrected at https://github.com/JuliaLang/julia/blob/735847010c84ad6b54ff675d713346ffe8981d07/doc/manual/parallel-computing.rst but, it does not appear to be the case that this flows through to the front-page matter at http://julialang.org in particular,

[julia-users] Re: Understanding QML.jl

Hi Uwe, See below for inline answers. As a general note, I mostly started the QML module as a proof-of-concept and a real-world test for CppWraper (soon CxxWrap.jl). I'm having a lot of fun with it at the moment, but I can't promise I'll be able to turn this into a feature-complete GUI

[julia-users] Re: Embedding Julia

For me it worked that way: 1. unzipped julia to a destination folder. In my case: /opt/julia/julia-2ac304dfba/bin 2. put $JULIA_HOME into ".bashrc": export JULIA_HOME=/opt/julia/julia-2ac304dfba/bin export PATH=$PATH:$JULIA_HOME *NOTICE:* the $JULIA_HOME variable already has to contatin /bin

Re: [julia-users] Re: metaprogramming update variable when slider changes

But I want to code in atom and render the chart with PyPlot, not jupyter notebook. Also, I would just like to know how to do this. On Friday, March 25, 2016 at 12:00:50 PM UTC-7, Stefan Karpinski wrote: > > You may want to check out Interact.jl: > https://github.com/JuliaLang/Interact.jl > >

Re: [julia-users] Determine the module where a type is declared

On Fri, Mar 25, 2016 at 3:00 PM, David Anthoff wrote: > Hi, > > > > I’m looking for a function that gives me back the module where a given type > is declared. For example, if I call something like > > > > type_module(Float64) Not an official API but `Float64.name.module` >

Re: [julia-users] Re: metaprogramming update variable when slider changes

You may want to check out Interact.jl: https://github.com/JuliaLang/Interact.jl On Fri, Mar 25, 2016 at 1:59 PM, Lewis Lehe wrote: > Err that is > > slider[:on_changed]( >#WHERE I WANT THE MACRO TO GO >variable = slider.val > ) > > > > On Friday, March 25, 2016 at

[julia-users] Determine the module where a type is declared

Hi, I'm looking for a function that gives me back the module where a given type is declared. For example, if I call something like type_module(Float64) I'd like the function type_module to return the module where Float64 is defined. Essentially, I'm just looking for the equivalent of

[julia-users] Re: raytracing in julia

I wrapped FireRender.jl , which uses FireRays to do the hit detection. The C-Interface of FireRender was very nice to wrap and got me started very quickly,

[julia-users] Re: metaprogramming update variable when slider changes

Err that is slider[:on_changed]( #WHERE I WANT THE MACRO TO GO variable = slider.val ) On Friday, March 25, 2016 at 10:57:34 AM UTC-7, Lewis Lehe wrote: > > Hi, > I am learning about metaprogramming and macros. I have a very basic case > but am unsure about what Julia is capable of.

[julia-users] metaprogramming update variable when slider changes

Hi, I am learning about metaprogramming and macros. I have a very basic case but am unsure about what Julia is capable of. last time I asked a question here I got a very helpful answer shortly. I am making sliders for a matplotlib plot. I would that when a slider changes, it changes some the

[julia-users] Understanding QML.jl

The development of the QML bindings (see: https://github.com/barche/QML.jl/) make nice progress. I have some general questions: 1. When shall I use Julia strings, when a QByteArray? 2. Are some or all methods of QT classes, e.g. of QByteArray exposed to Julia? If only a subset of the

Re: [julia-users] How to copy a DataFrame structure in an empty DataFrame

Le vendredi 25 mars 2016 à 08:26 -0700, Fred a écrit : > Thank you tshort. Is there a website or email address to post > requests concerning documentation ? Use the GitHub project for that. Note you can make pull requests by editing the documentation online too. Regards > > Feel free to file

Re: [julia-users] ANN: Quantumoptics.jl - a quantum optics toolbox for julia

I don't know much about Quantum Optics beyond the fact that they were essential in seeing gravity waves. I do know nice docs -- and yours are. On Thursday, March 24, 2016 at 3:12:48 PM UTC-4, Sebastian Krämer wrote: > > Okay, thanks again. > > I also followed your advice and renamed the project

Re: [julia-users] How to copy a DataFrame structure in an empty DataFrame

Thank you tshort. Is there a website or email address to post requests concerning documentation ? Le jeudi 24 mars 2016 19:28:44 UTC+1, tshort a écrit : > > Feel free to file issues for missing documentation or (even better) pull > requests. > >

Re: [julia-users] Re: Status of Plots.jl?

There was a problem with the Atom setup... it should be fixed on the dev branch now. Please let me know if it works for you. (it worked for me) On Fri, Mar 25, 2016 at 9:14 AM, Josef Heinen wrote: > Which platform are you using? Please try to checkout the master branch: >

Re: [julia-users] Re: Status of Plots.jl?

Which platform are you using? Please try to checkout the master branch: Pkg.checkout("GR") On Wednesday, March 23, 2016 at 8:24:27 AM UTC+1, Dupont wrote: > Hi, > > I tried your dev branch as suggested, > > julia> Pkg.status("Plots") > - Plots 0.5.3+ dev >

[julia-users] Re: Tools for creating presentation slides with Julia code?

I've used Beamer with LaTeX and a custom program listing for syntax highlighting with success.

Re: [julia-users] Registering / renaming CppWrapper

Thanks for the feedback, I'll probably do the rename to CxxWrap.jl tomorrow, so the ship is just about to sail ;) On Friday, March 25, 2016 at 1:18:41 PM UTC+1, Stefan Karpinski wrote: > > The ship may have sailed on giving feedback on this name too ;-) > > Personally, I just think "cxx" is

[julia-users] raytracing in julia

I need to do things like building a simple geometry which consists of a few polygons, cylinders, spheres and calculate if/where rays hit these objects. Is there some julia library which does this already? Or some easy to wrap C/Fortran library? Any suggestions? I would prefer a solution, which

[julia-users] Re: To solve optimization problem in julia is it necessary to add any module.

It depends on what kind of problem you'd like to solve and how you'd like to solve it. - JuMP is a modeling interface that lies between you and a dedicated solver. JuMP lets you easily specify your problem, sends that problem to the solver, and retrieves output for you. JuMP itself is not a

[julia-users] HTTP/2 for Julia, Compatibility First or Unified API First

Hi Julia users, I'm planning to implement HTTP/2 support for Julia (and hopefully as a GSoC project!), extending the HTTPServer.jl and Requests.jl library. I need to make a design decision about whether I should put compatibility first with existing APIs, or I should design a new unified API.

[julia-users] is there a video showing how to configure the development environment for julia

is there a video showing how to configure the development environment for julia

Re: [julia-users] Registering / renaming CppWrapper

The ship may have sailed on giving feedback on this name too ;-) Personally, I just think "cxx" is cooler that "cpp". Add that to being more correct, and it's a winner for me as an extension for C++. On Fri, Mar 25, 2016 at 2:17 AM, Jameson wrote: > Cpp sounds fine to me.

[julia-users] To solve optimization problem in julia is it necessary to add any module.

For the solving of optimization problems in julia is it necessary to add any module first such as jump , NLopt or any other ?? If it is necessary to add then which one is best ? Best Regards, Tanveer Iqbal

[julia-users] from 0.4 to 0.5

Hello colleagues, i'm currently looking into the 0.4/0.5 transition (on my own code first, but) and i'm missing the big picture how to deal with syntax/language changes. Someone pointed out, Gadfly isn't usable (in 0.5 recent) and looking into Compose i see at least in one place (the makeform

Re: [julia-users] Registering / renaming CppWrapper

Cpp sounds fine to me. That's the only file extension accepted by gnu make (even the expected tool name is CXX): https://www.gnu.org/software/make/manual/html_node/Catalogue-of-Rules.html#Catalogue-of-Rules I think ship sailed a long time ago for cpp being an unambiguous abbreviation for the

Re: [julia-users] macroexpand entire module

as a tech demo project (prior to precompilation being on master), I created a package around this idea (but with the output going to a file instead of the screen) with handling for some bonus concepts, like recursing through submodule definitions, tracking file/line number information, and