http://www.perlmonks.org?node_id=954435


in reply to Re^2: Module provides both of functional interface and object-oriented one
in thread Module provides both of functional interface and object-oriented one

On the other hand, there's nothing that forbids you from creating wrappers which you can export. Adding to my previous code:

@EXPORT_OK = qw/get_bar/;

sub get_bar {
    my $var = shift; # your $blosxom::header hashref
    bar($var, @_);
}

[download]
  • Comment on Re^3: Module provides both of functional interface and object-oriented one
  • Download Code

Replies are listed 'Best First'.
Re^4: Module provides both of functional interface and object-oriented one
by anazawa (Scribe) on Feb 17, 2012 at 08:51 UTC
    If a module looks as follows: 
    package Foo;
@EXPORT_OK = qw(get_foo);

sub new {
    # constructer
}

sub get {
    # for OO interface
}

sub get_foo {
    # for procedural interface
}

1;

    [download]
    users may write as follows: 
    $o = Foo->new();
$o->get($key);     # of cource, $value
$o->get_foo($key); # what's this?

    [download]
    If users choose OO interface, they shouldn't be able to call 'get_foo' method. How can I solve this problem?
[reply]
[d/l]
[select]

      If users choose OO interface, they shouldn't be able to call 'get_foo' method. How can I solve this problem?

      I'm not very well versed in Perl's OO, so someone please correct me if I'm wrong, but I don't think you can forbid users from calling it. The only thing you can do is throw an error on unexpected arguments.

      (There is a convention that a class's private methods' names begin with the underscore character, though.)

[reply]

In Section Seekers of Perl Wisdom