Re: Re: aliasing subs

[december]

But the problem is that in the current form, all output comes from one pattern match. The base sub has to return either $a or $b, $pathname or $filename; if I use wrapping subs, I still loose the context.

Unless ofcourse I add an extra parameter that specifies whether I'm interested in the pathname or the filename, but then I don't need the wrapping subs either.

I could make seperate subs obviously, but then I would have to duplicate the same pattern matching, and that wouldn't be much fun training-wise, would it. ;)

[edan]

The base sub has to return either $a or $b, $pathname or $filename

Err... no.

sub do_the_match
{
    my $dir = shift;
    my ($path, $name) = ($dir =~ /(.*)\/([^\/]*)$/);
    return ($path, $name);
}

--
3dan

[december]

Yes, I'm sorry. I meant *must* return, by my own specification. I know I can return a list, but I think that would make using the function a bit harder, since I usually only need either the path or the file.

That's what complicates the matter; the output depends completely on what name was used to call the function, so if I can't find that out, my implementation is quite useless.

It's something that I would like to see implemented in a new version of Perl, though. I think it would be handy in some cases... More clear to read than anonymous subs.

[jdporter]

That's not exactly true. Consider:

  sub match {
    my $context = (caller(1))[3];
    my $arg = shift;
    my @result = $arg =~ /$pattern/; #
    $context =~ /dirname/  ? $result[0] :
    $context =~ /basename/ ? $result[1] : ... # etc.
    # otherwise, return the whole result vector:
    @result
  }

  sub dirname  { &match }
  sub basename { &match }
  # etc.

jdporter
The 6th Rule of Perl Club is -- There is no Rule #6.