in reply to Foo is not a Bar, why?

This is the same "problem" as: 
    print "The colour is ", colour (), "\n";
    ...
    my $colour = "red";
    sub colour {$colour}

[download]
And that has nothing to do with objects being bolted on.

Abigail

Replies are listed 'Best First'.
Re: Re: Foo is not a Bar, why?
by hardburn (Abbot) on Dec 18, 2003 at 21:51 UTC

    The fact that inheirtance is done at all through a package variable is where the bolted-on part comes in. Perl just does too much OO stuff at runtime, which ends up being a very good Perl system but not a great OO system.

    ----
    I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
    -- Schemer

    : () { :|:& };:

    Note: All code is untested, unless otherwise stated

[reply]
[d/l]

      Would you consider Smalltalk a "not great OO system"? It does even more at runtime.

      Also, if Perl 5 introduced both packages and objects, how could objects be "bolted on"? Packages exist, in part, to make objects possible, without requiring OO coding!

[reply]
      You will never hear me saying Perl's OO system is anywhere near half decent. But the problem pointed out by liz isn't an OO specific problem - it can happen with non-OO code as well.

      Abigail

[reply]

In Section Meditations