Your code should work as planned when called as Name::Name->new()

Class->method() works differently from Class::method only in that:

1) Class->method(@args) respects inheritance.

2) Class->method(@args) inserts "Class" as the first argument while Class::method() does not.

update: most people expect new() to be the constructor so it should return $self.

Your right it does work now. I'm not sure why it wasn't working before, more annoyingly I can't remember what error I was getting. I made a few changes before trying again and it works as I originally planner. How strange, there must of been something I changed. If I get the error again I'll post it here for future ref by anyone who reads this thread.

With Name::Name->subroutine() you need to capture the class name as the first argument in subroutine() method.

package Name::Name;
sub subroutine {
  my $class = shift; # shifting @_
  print $class, "\n";
}

package main;
use Name::Name;
Name::Name->subroutine();

# output:
# Name::Name
[download]

It's callled class method calling. With Name::Name::subroutine(), you call subroutine() with fully qualified package name without any argument.

I'm not sure what's missing, but if the subroutine in question is new() then you can't call it Name::Name::new() as it expects the class name as its first argument. Similiar way to the class method calling above is Name::Name::new('Name::Name').

---

Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!

package Name::Name;

use 5.6.0; # Always specify the minimum Perl your code expects to work
+ with.

use strict; # Got this right.
use warnings FATAL => 'all'; # If you're 5.6+, this catches a lot of s
+illy mistakes.

our $VERSION = '0.05'; # If you're 5.6+, this is a nicer way of writin
+g that VERSION stuff.

# MY CODE HERE

1;
__END__ # Always put this here to tell you that there can never be any
+ code after this.
[download]

Now - why do you want to call the methods Foo->meth() vs. having it be a library of functions? I've always thought that the way File::Spec does this is really freaking annoying. If you're a library of functions, then provide the functions for export. If you're an OO module, then use Moose (or any of the other 1235123123 OO modules on CPAN) to provide the OO stuff, have your users receive an object, and call methods on that. Just because you can do something is a poor reason to actually do it, especially in production. KISS is a good motto.

I've added use '5.004'. I Already had __END__ (in my version anyway). I wont use 'our', I used it in the past and hit problems when installing my scripts on machines with older copies of Perl. Now I stick to 'use vars'.

The module users do receive an object they call methods on.

use 5.6.0;

Just FYI - This actually breaks in 5.10, it should be 5.006. Here is what the docs say about it.

v-string in use/require is non-portable
(W portable) The use of v-strings is non-portable to older, pre-5.6, Perls. If you want your scripts to be backward portable, use the floating point version number: for example, instead of "use 5.6.1" say "use 5.006_001". This of course won't help: the older Perls won't suddenly start understanding newer features, but at least they will show a sensible error message indicating the required minimum version.

-stvn

Reading them now, would have read them in the first place if I knew which ones were relevant to what I'm trying to do.