$this->{mess}
The "object oriented" stuff, while making it more powerful, looked like modem line noise, and created a half-dozen new ways to say the same thing. It drifted away from the shell-like nature of Perl 4, and lost a lot of clarity.
Useless trivia. Both the . and the -> notations for OO programming have their roots in C. If foo is a struct, and bar is a property of the struct, foo.bar pulls that property out. If baz is a pointer to foo, then baz->bar does likewise.
In Perl the . was already taken for string concatenation, so -> was the next reasonable choice. And the analogy is surprisingly exact. For example if $foo = $bar = {} then calling bless($foo) will also bless $bar since both are just references to the actual object.
As for lots of ways to say the same thing, TIMTOWTDI was an intentional goal.
At that point, you might as well start using a heavier language.
You rarely write accessor methods yourself in Perl 5. In Perl 6, you describe your accessors/mutators in the class definition:
class Pointer {
has $.x; # a ro accessor
has $.y is rw; # a rw mutator
}
Which, by the way, is now faster than Perl 5.> has $.y is rw; # a rw mutator
Opinion: I don't like the asymmetry of that, although I do understand that having to write "is ro" too, would make the language slightly more verbose.
Python has something similar with the syntax for properties; don't like that syntax too, for the same reason (asymmetry).
E.g.: The 2nd code example in the question here -
https://stackoverflow.com/questions/17330160/how-does-the-pr...
- the one that uses
@x.setter
I'm not a language designer or close to it, though, just saying. multi sub trait_mod:<is> (Attribute:D $attr, :$ro!) {
# no need to do anything, because this is the default
}
class Pointer {
has $.x is ro;
has $.y is rw;
}
That is assuming you aren't fine with using `is readonly`. class Pointer {
has $.x is readonly;
has $.y is rw;
}
Which works better with the trait mod `is required` class Pointer {
has $.x is readonly is required;
has $.y is rw;
}
Interesting. Can you elaborate a bit on what changes made 5 worse than 4, in your opinion?
>Perl 4 also spoke Sybase really well, which made it our reporting tool of choice. We could grab whatever from our Sybase databases, and format nice printed/screen reports easily in Perl.
Can confirm that about Perl and Sybase, anecdotally. A friend worked at banks in Singapore and Japan that used sybperl, which was a way to use Sybase from Perl. IIRC he said it made writing DB-related programs easy.