package Ivy; # in Ivy.pm
  
  { 
    no strict 'refs';
    *{"Xxx::Ivy::"} = *{"Ivy::"};
  }
[download]

That should handle most exporting and inheritance issues by making the two packages equivalent...

*{"Xxx::Ivy::"} = *{"Ivy::"}; is this different from the previous proposal based on use base Net::Ivy; ?

Where is it possible to find the doc of the 'use base ...;' construct?

... is this different from the previous proposal...

Yes. The "use base" technique makes one class inherit from the other, whereas this technique makes the two namespaces equivalent.

A key difference is that inheritance only works for method calls, whereas namespace aliasing works for both methods and function calls.

Where is it possible to find the doc of the 'use base ...;' construct?

The base module is included with Perl, so you should be able to run perldoc base for documentation.

Originaly Ivy.pm was only function based and it was only possible to use one Ivy bus. It has been extended so that this functionnal interface still works, but usually we are now using a class/instance interface style. Usually there is only one instance of Ivy bus. I think the main exception is when we developped some GUI applications plug-in's. In those plug-ins' a new part of the GUI is added as an external module, and this GUI part is communicating through new instances of Ivy.

In my current knowledge of perl and according many responses to my quest, I am sure building a full wrapper is possible. The real point now is whether it is worth such complexity as currently this module is quiet simple to understand. My feelings are it does not deserve such complexity if the Ivy name could become a new root name in the CPAN.

Any way, I will ask the question on the appropriate mailing list on the CPAN.