Hello colleague,
merci, that was the discussion i was looking for (#14472 from Tim is in a
similar area).
I do not have a clear need, otherwise i would have a full example. However
this providing optional functions in modules - which is the only 'real'
encapsulation mechanism in Julia shows up
Le lundi 21 mars 2016 à 03:19 -0700, Andreas Lobinger a écrit :
> Hello colleague,
>
> sorry i wasn't clear enough. I'm aware of the MoO for packages and
> extensions and i'm a great fan of modularisation. However the topic
> of optional include/import or something like "require" (deprecated)
> is
Hello colleague,
sorry i wasn't clear enough. I'm aware of the MoO for packages and
extensions and i'm a great fan of modularisation. However the topic of
optional include/import or something like "require" (deprecated) is still
around. Not everything can be formulated into a tree of dependenci
If you want to add functions to the Cairo module, open pull requests or use
your fork for the time being. eval'ing into modules that aren't yours is not a
good practice. You can create a CairoExtensions.jl package that depends on
Cairo and uses its copy of libcairo.
No.
More concrete, i want to put another function into Cairo and i want to
avoid to load a second time libcairo.so.
On Sunday, March 20, 2016 at 1:01:58 PM UTC+1, Gregory Salvan wrote:
>
> Hi,
> when you want to add methods on Base module (like getindex, getfield...)
> you use "import Base.get
Hi,
when you want to add methods on Base module (like getindex, getfield...)
you use "import Base.getindex" then write a new function with new types
args.
for exemple to add methods in B.jl on functionA from A.jl
import A.functionA
function functionA(...)
end
Is what you were looking for?
Le
