I'm following the list traffic for Perl6 and I'm getting a little worried. . .

Perl was my first real language. I programmed HTML, BASIC, Delphi, and started learning C and noticed how cool perl was. If they rip out the internals as the following suggests, how much will I have to relearn to keep with Perl? 

> And I'm *really* against . as an attribute access mechanism :-)

This is my stance as well. 

One thing to remember is that we're ripping the internals out
completely. This means we can redo everything, including the fact that
Perl OO is basically "bolted onto the side" as you mention (it is,
indeed).

I absolutely hate . as well. I always have, even in other languages. The
-> notation is much clearer that "hey, we're doing something with a
member attribute".

If what you're looking for is something like this:

   $foo->bar = "hello";    # ignoring if bar() is a func, or hash, or
???

I don't see why we can't do that. Just rewrite the internals (hey, we're
doing that anyways!). And personally, I'm for this type of thing because
you can say:

   ($foo->bar, $foo->bar2) = split;

Without having to worry "is it a function? hash? array?". And we can
still leave:

   $foo::bar = "scalar";
   @foo::bar = ("array");

For people that want tight control over this stuff.

I agree with Damian. I think the idea of putting two distinct OO methods
in Perl is a very bad idea, at best. Fixing some stuff about the current
mechanism is, however, a very good idea. I think the RFC would be much
better spent if it listed annoyances and proposed fixes, rather than a
second whole OO scheme. Remember, we're trying to *decrease* bloat here.
:-)

I wouldn't worry about breaking stuff at this point. That's a next-stage
decision - benefits vs. costs. We're still in the "developing ideas"
stage. Remember, we're got conversion scripts, FAQs, Camel-4, and lots
of other ways to bring people up to date on changes.

-Nate

I'm not sure I want to relearn Perl and I'm not sure I'll like the new Perl as much as I like this one. I'm sure lwall knows what he's doing, Nate knows what he's doing, Randal is keeping an eye on things and all are very good, but I'm concerned about the effect this rewrite will have on my daily life, on script usage, and the like. 

J. J. Horner
Linux, Perl, Apache, Stronghold, Unix
jhorner@knoxlug.org http://www.knoxlug.org/

In reply to Ripping out Perl internals in Perl6 by jjhorner

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.