Bug #28394 for MRO-Compat: Allow optional exporting

Fri Jul 20 01:11:30 2007 mschwern [...] cpan.org - Ticket created

Subject:

Allow optional exporting

MRO::Compat does not export anything by default, but it would be nice if it allowed the user option of asking for functions to be exported by listing them in @EXPORT_OK.

Tue Jul 24 00:41:34 2007 blblack [...] gmail.com - Correspondence added

On Fri Jul 20 01:11:30 2007, MSCHWERN wrote: Show quoted text

> MRO::Compat does not export anything by default, but it would be nice if > it allowed the user option of asking for functions to be exported by > listing them in @EXPORT_OK.

I suppose mro::import (MRO::Compat's version and the one in the perl core, they need to be compatible) could optionally export the mro::* funcs. I hadn't set it up this way from the beginning because (a) "mro::" is 5 characters, and (b) I'm not a big fan of function export/import, but I could be convinced otherwise.

Tue Jul 24 00:41:37 2007 The RT System itself - Status changed from 'new' to 'open'

Tue Jul 24 00:41:40 2007 blblack [...] gmail.com - Given to BLBLACK

Sun Sep 09 12:00:29 2007 blblack [...] gmail.com - Correspondence added

Offering the export would mean an interface change for MRO::Compat, which I can't do without changing the interface of mro.pm in 5.10 as well (since the whole point of MRO::Compat is to offer an identical interface to that), and it's a bit late in the game for any changes there, so I think this is just how it will have to be.

Sun Sep 09 12:00:31 2007 blblack [...] gmail.com - Status changed from 'open' to 'resolved'

Sun Sep 09 18:01:13 2007 mschwern [...] cpan.org - Correspondence added

From:

MSCHWERN [...] cpan.org

On Sun Sep 09 12:00:29 2007, BLBLACK wrote: Show quoted text

> Offering the export would mean an interface change for MRO::Compat, > which I can't do without changing the interface of mro.pm in 5.10 as > well (since the whole point of MRO::Compat is to offer an identical > interface to that), and it's a bit late in the game for any changes > there, so I think this is just how it will have to be.

I would understand if this was modifying or taking away a feature, but this is just adding purely optional exports. However, I just took a look at mro.pm for the first time. What I did not know is that mro already uses import to control the pragma rather than export. That would make wedging in function export syntax difficult. Now I see where the miscommunication lies and why you said it's not worth it. Request dropped. Sorry to bother.

Sun Sep 09 18:01:16 2007 The RT System itself - Status changed from 'resolved' to 'open'

Thu Sep 13 15:04:57 2007 blblack [...] gmail.com - Correspondence added

OK :)

Thu Sep 13 15:05:16 2007 blblack [...] gmail.com - Status changed from 'open' to 'resolved'