Re^2: Undefined subroutine errors

None of the functions provided by Exporter are called in your snippet. Why bother using Exporter?

Update: In answer to my question, I suppose it gives the Green Goblin and other third parties the ability to import from these modules, but it detracts from the point of using fully qualified function names.

Comment on Re^2: Undefined subroutine errors

Replies are listed 'Best First'.
Re^3: Undefined subroutine errors by leriksen (Curate) on Oct 26, 2005 at 03:11 UTC
In this case no, but that doesnt stop someone else using Spiderman or DrOctopus with the full export. As I said, it fixes his problem, YAWTDI, but not a great way. ...reality must take precedence over public relations, for nature cannot be fooled. - R P Feynmann	[reply]
Re^4: Undefined subroutine errors by ikegami (Patriarch) on Oct 26, 2005 at 03:15 UTC
All you need to do is put `BEGIN { ... }` around `our @EXPORT = ...` (and remove the `()` from the `use` statements) and it works without fully qualified function names.	[reply] [d/l] [select]