Lyle Kopnicky wrote:
> Thanks for your reply. But supposing I'm going to keep each class in
> it's own file, what is the advantage of making that file a module?
Have you read the man pages on modules ?
perlmod Perl modules: how they work
perlmodlib Perl modules: how to write and use
perlmodstyle Perl modules: how to write modules with style
perlmodinstall Perl modules: how to install from CPAN
perlnewmod Perl modules: preparing a new module for
distribution
ANd OO stuff:
perlboot Perl OO tutorial for beginners
perltoot Perl OO tutorial, part 1
perltooc Perl OO tutorial, part 2
perlbot Perl OO tricks and examples
> Doesn't that just let me import the methods of the class into my own
> namespace, from another file? That would be weird - they're supposed to
> be methods of a class. They belong in the class' namespace, not mine.
In Perl you have the concept of packages which you can read about in
the above references. A package would house a class and its methods.
Packages have their own name space. Packages and modules can be
thought of as the same thing basically when you're using OO. But I'm
no expert on OO terminology.
_______________________________________________
Perl-Win32-Users mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
