Re: Why should I use Exporter?

You're right--for OO modules, you usually wouldn't use Exporter. There are plenty of perfectly good modules out there that never touch the thing. Though even in an OO module, you might want to use it because:

Creating a secondary functional interface (like what CGI.pm does)
Allowing certain constants to be accessible outside your module
Other reasons (???)

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

Note: All code is untested, unless otherwise stated

Comment on Re: Why should I use Exporter?

Replies are listed 'Best First'.
Re^2: Why should I use Exporter? (don't mix interfaces) by Aristotle (Chancellor) on Jun 18, 2003 at 22:02 UTC
Creating a secondary functional interface (like what CGI.pm does) I don't like this at all. If you want to provide a secondary functional interface, please add a Foo::Bar::Functions or Foo::Bar::Simple module or some such instead. That way, the baggage doesn't have to be dragged around by everyone who probably doesn't even need it, nor adds extra mess in the main module to maintain. It also, and this I consider the greatest benefit, signficantly reduces the temptation to do dangerous and crufty things like trying to have one and the same subroutine handle both OO and non-OO calling conventions. Makeshifts last the longest.	[reply]

Replies are listed 'Best First'.

Re^2: Why should I use Exporter? (don't mix interfaces)
by Aristotle (Chancellor) on Jun 18, 2003 at 22:02 UTC

Creating a secondary functional interface (like what CGI.pm does)

Makeshifts last the longest.

[reply]