in reply to Re: perl module structure (Façade choosing backend)
in thread perl module structure

Yes it’s rather abstract because I’m looking for general solution. I think what I’d like to do is something similar to java collection. List is an interface and there are multiple concrete implementations. So I might have pure perl and xs backend implementations. I just remember there’re some Perl modules if xs is available it’ll use xs backend implementation otherwise using pure perl.

Update

Design pattern wise, I am thinking of abstract factory pattern. There’ will be factory, products interfaces and of course actual concrete implementations.

  • Comment on Re^2: perl module structure (Façade choosing backend)

Replies are listed 'Best First'.
Re^3: perl module structure (Perl ne Java)
by LanX (Saint) on Mar 30, 2018 at 13:34 UTC
    > I’m looking for general solution

    Sorry, this sounds like you are looking for a way to do Java in Perl. Many answers in the Java world don't apply to Perl because the questions don't arise.

    And it's not clear for me HOW the implementation should be chosen. automatically or by users choice.

    > List is an interface and there are multiple concrete implementations.

    Not an issue in Perl because it doesn't have static typing of the list elements.

    > I think what I’d like to do ...

    Please think harder what you want and show some Perl code exemplifying it.

    Most of us don't "speak" Java... ;-)

    Cheers Rolf
    (addicted to the Perl Programming Language and ☆☆☆☆ :)
    Wikisyntax for the Monastery

[reply]

In Section Seekers of Perl Wisdom