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 dependencies that exist on all systems. I'm experimenting with libxcb (so close to X11) and i assume this will not be available for MS-Windows based systems.
But i'm still trying to find this in the issues. On Monday, March 21, 2016 at 9:45:40 AM UTC+1, Tony Kelman wrote: > > 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.
