Clovis_Sangrail has asked for the wisdom of the Perl Monks concerning the following question:

I am going thru the Alpaca book, currently trying out the examples of objects/instances. The packages (or classes) defined in the text are typically written as:

{ package somename;
     #perlcode
}

[download]

I'm used to seeing things analagous to the 'package' keyword (ex 'sub') outside of the block of code. I find that Perl (or my example programs, at any rate) run identically with the syntax of the packages written as above (from the textbook) or in any of the following ways: 

package somename;
{
     #perlcode
}

package somename
{
     #perlcode
}

package somename
{
     #perlcode
};

{ package somename;
     #perlcode
};

[download]

I do get syntax errors with the following:

{ package somename
    #perlcode
}

[download]

When the package keyword is inside the block it seems you have to have a semicolon after the package/class name. But I am surprised that so many other variations all work. My question is, am I introducing some kind of subtle difference in scope or something like that? Are they really all the same?

Replies are listed 'Best First'.
Re: OO Perl Baby Steps
by davido (Cardinal) on Jun 12, 2013 at 15:39 UTC

    Your usages have subtly different semantic, and in some cases, practical meanings, especially if you're using Perl 5.14 or newer.

    { package somename; ..... }: This creates a lexical scope, and inside that lexical scope you happen to be working with package somename. When the block ends, you will be working back in the previous package again, though this is not the preferred syntax (see below) as of Perl 5.14.

    package somename; { ..... }: This declares that you're working with package somename, and then creates a lexical scope. The two are not really related to each other, but it does happen that this lexical scope was created while you're working in package somename.

    package somename { ..... }: This is a new Perl 5.14 feature; you've declared that you'll be using package somename for the duration of the following block (I suppose you could change within the block, but haven't tried). Once the block expires, the package you will find yourself working within will revert back to whatever was in effect before this package block.(See http://www.perl.com/pub/2011/05/new-features-of-perl-514-package-block.html).

    The next two are just the same as other constructs you demonstrated, but with an extra semicolon at the end, which has no effect. You can put a semicolon just about anywhere you want as long as it doesn't break a statement. print "hello world\n" ;;;;;;;;;;;;; print "Hello again\n";;;;;; # Perfectly legal

    The last one is a syntax error because you didn't separate the "package somename" statement from the next statement with a semicolon. It's not a syntax error if that statement is the last statement within the block, since semicolons are optional for the final statement in a block.


    Dave

[reply]
[d/l]
[select]
Re: OO Perl Baby Steps
by cdarke (Prior) on Jun 12, 2013 at 15:27 UTC

    In Perl, the semi-colon ; is not a statement terminator, as it is in languages like C, C++ and Java, it is a statement separator, as it is in Pascal and UNIX shells.

    So, the last statement in a block does not require a semi-colon after it. It is a good idea to put one in though, because someone (maybe you) later will add another statement and get a syntax error.

[reply]
Re: OO Perl Baby Steps
by choroba (Cardinal) on Jun 12, 2013 at 15:45 UTC 
    package somename
{

    [download]
    is a recent addition (introduced in 5.14) and is equivalent to
    { package somename;

    [download]

    Moreover, 

    package somename;
{

    [download]
    is different if there is some code after the closing } - it still belongs to the package.
    لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ
[reply]
[d/l]
[select]
Re: OO Perl Baby Steps
by Clovis_Sangrail (Beadle) on Jun 14, 2013 at 16:45 UTC

    Thanks, this is informative. I tested it out and saw that with "package pkgname;" just above the block of my parent class, I could move methods out to below the block of code and child classes could still inherit them. That's probably not a good idea. I guess the book's notation, with the package directive inside the block, is the most suggestive of the idea that the methods are specific to the class. That's probably what I'll stick with, and use 'package' statements outside of a block just for namespace (rather than OO Perl) purposes. But it's good to know about the new 5.14 syntax.

[reply]

      Perl was not necessarily designed to be Object Oriented, and the addition of OO to Perl has been called by some a hack at best. If this concern of yours about packages is great enough then i instead invite you to use the declarative syntax for Moose, MooseX::Declare.

      jeffa

      L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
[reply]
[d/l]
[select]

        I do want to check out Moose and MooseX (I'm tempted to call it 'Moose++'), it seems like alot of people use it. But I first want to get thru the, err, 'official' implementation of OO Perl as described in the Alpaca book.

        As I was reading the book and got to the section on closures, I thought to myself: "Ahh, this is how they are going to do private variables in a class." Then it turns out that it doesn't work that way at all. The private data is just all the fields in the whatever-it-is that the blessed reference references. And some people complain that it isn't as really private as they'd like.

        I'm surprised that there is not more use of closures. OTOH, maybe that would not work well with inheritance? In Googling about on the issue I see that I'm far from the first person to think about this. Well, exploring that question is likely much further over my head at this point than is Moose.

[reply]

Back to Seekers of Perl Wisdom