Re: [julia-users] conflicts when reloading module

2016-09-19 Thread Cedric St-Jean
Any progress on that? 0.5 killed Autoreload, and I am looking for alternatives. Have you tried julia with babel? On Wednesday, February 18, 2015 at 9:27:05 AM UTC-5, Tamas Papp wrote: > > The problem with workspace() is that if I am loading a few modules, then > re-initialization time is nontriv

Re: [julia-users] conflicts when reloading module

2015-02-18 Thread Tamas Papp
The problem with workspace() is that if I am loading a few modules, then re-initialization time is nontrivial. Eventually I will have to extend ESS to eval into modules, so now I am working on that. thanks, Tamas On Wed, Feb 18 2015, Tim Holy wrote: > As you noted, if you scope every call by

Re: [julia-users] conflicts when reloading module

2015-02-18 Thread Tim Holy
As you noted, if you scope every call by the module name (Foo.baz() rather than baz()), then you will be fine. Or use the workspace command. http://docs.julialang.org/en/latest/manual/workflow-tips/#a-basic-editor-repl-workflow --Tim On Wednesday, February 18, 2015 09:53:24 AM Tamas Papp wrote:

Re: [julia-users] conflicts when reloading module

2015-02-18 Thread Mike Innes
If you use Juno you can eval into modules directly, without having to reload them, which makes stuff like this a lot nicer. AFAIK there's no other way to work around this, but I'd love to be corrected on that. On 18 February 2015 at 08:53, Tamas Papp wrote: > Hi, > > I thought that using modules