Re^3: Module development: concurrent versions (Updated)

...you cannot use the two versions in the same program.

In that case, the only option I see is to give them different names/namespaces (temporarily), because you generally can't load two versions of a shared lib (with same name and exported symbols) twice, or load two Perl packages into the same namespace...

Comment on Re^3: Module development: concurrent versions (Updated)

Replies are listed 'Best First'.
Re^4: Module development: concurrent versions (Updated) by BrowserUk (Patriarch) on Dec 23, 2010 at 11:04 UTC
Indeed. That's what I've done. But--unlike say a C dll--because there are so many internal self-references, and cross-references in makefiles, meta-files and other random pieces of build mechanism arcanery, it is a time consuming and laborious process to "rename" a module. I just thought, (hoped), someone might have come up with a better mechanism than doing it manually. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]

Replies are listed 'Best First'.

Re^4: Module development: concurrent versions (Updated)
by BrowserUk (Patriarch) on Dec 23, 2010 at 11:04 UTC

Indeed. That's what I've done.

But--unlike say a C dll--because there are so many internal self-references, and cross-references in makefiles, meta-files and other random pieces of build mechanism arcanery, it is a time consuming and laborious process to "rename" a module.

I just thought, (hoped), someone might have come up with a better mechanism than doing it manually.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

[reply]