Hello colleauges,
On Wednesday, July 23, 2014 6:18:03 PM UTC+2, Stefan Karpinski wrote:
On Wed, Jul 23, 2014 at 6:06 AM, Andreas Lobinger lobi...@gmail.com
javascript: wrote:
In principle i agree, everything that is defined in the Modules is usable
regarding its own namespace. But then,
Hello collague,
On Tuesday, July 22, 2014 4:25:46 PM UTC+2, Mauro wrote:
I agree that there should be some means of resolving conflicts (by
warning,
by precedence) but just dropping a whole set of methods because they
conincidentially have the same name AND at the same time advertising
There is another option, which won’t necessarily work for plot but might
resolve many other issues (and is frequently used on functions like push!):
make both modules import a common function to extend.
What took me a while to understand in this context, is the distinction
between a
On Wed, Jul 23, 2014 at 6:06 AM, Andreas Lobinger lobing...@gmail.com
wrote:
In principle i agree, everything that is defined in the Modules is usable
regarding its own namespace. But then, why do we have the export of
functions? It's not even needed...
If you strictly prefix all functions
The problem is that both Gtk and Gadfly exports a draw function. Internally
those are scoped by module so that their name is Gadfly.draw() and
Gtk.draw(), and you can call them as such in your code. We can't merge the
function's method, because there is no way to know which one to call if
both
Isn't it odd, though, that there is no warning Could not import
Gadfly.draw into Main (or Gtk.draw, depending on order)?
// T
On Tuesday, July 22, 2014 12:30:55 PM UTC+2, Ivar Nesje wrote:
The problem is that both Gtk and Gadfly exports a draw function.
Internally those are scoped by module
I agree that there should be some means of resolving conflicts (by warning,
by precedence) but just dropping a whole set of methods because they
conincidentially have the same name AND at the same time advertising
multiple dispatch in julia doesn't fit for me.
Multiple dispatch would still
