Slashdot Mirror


Perl 6 Synopsis 5

XaXXon writes: "perl.com has Synopsis 5 for Perl 6 up. It's a brief overview of all the changes made in Larry Wall's Apocalypse 5. Lots of stuff about the new regex syntax. I must admit, however, that I'm getting tired of reading about perl 6 -- I want to start using it." We posted Larry Wall's 5th Apocalypse in May.

9 of 203 comments (clear)

  1. Re:Does this mean... by Fjord · · Score: 5, Funny

    No. Perl is a write-only language. You aren't supposed to be able to read it ;)

    --
    -no broken link
  2. Rename it, it isn't Perl anymore by ToasterTester · · Score: 4, Insightful

    Wall has changed the language too much and now more regex changes. Like Pascal when major updates became Modula or later Oberon. Original Pascal was left to evolve on it own. Same with Turbo Pascal when Borland heavily changed it they changed the name to Delphi. Call Perl 6 the new beast that it is.

  3. Re:Perl 5 was nice by selectspec · · Score: 4, Insightful

    I don't pretend to know anything about Perl 6, and hopefully they are cleaning up Perl. However, I agree with your assessment of Perl 5: a thousand ways to do the same thing each using their own exclusive exotic ascii character combinations.

    One has to wonder about the relative success of Java, given its horrific performance and obscene installation complexity. However, ultimately Java's success comes down to the lack of choices in the language syntax and a strong networking library.

    Of course Java syntax is a simplification of C++, while Perl's roots are in shell scripts.

    I wish there was a shell with the simple grace of C, the libraries and idiot proof installing packages of Perl, and the portability of bash.

    --

    Someone you trust is one of us.

  4. Yeah..more RegEx fragmentation by Eol1 · · Score: 5, Insightful

    #sarcasm# Yeah!!! Just what we need more RegEx fragmentation #/sarcasm#

    Honestly, RegEx hasn't changed much since awk and when it did, Perl usually led the way. The changes though usually just added features or tweaks, my RegEx still basically looked the same though whether I used VIM, Python, ASP, C++, Perl, .

    Shortly after reading the changes, I was aghast. Sure some of the changes make sense but some are going completely against RegEx as we know them now (getting rid of character classes for one []) . Sure you can use the p5 modifier or do the funky syntax to use [] but the issue is its a radical change.

    This is a bad thing(tm). This is going to force all us RegEx people who currently using 4 or 5 different RegEx tools to not only learn minor differences based on each app, but we will be forcec to learn a COMPLETE DIFFERENT subset of RegEx syntax incompatible with anything else.

    Now wait you say, Perl has always led the way and other tools seem to use perl compatable RegEx libraries. Not so with Perl6. Have floated this question out on a couple developer lists (PHP for one) and everybody is saying, Perl 6 RegEx support isn't going to happen. They are all happy with the current state of RegEx's. This is especially go to cause hell with PHP's perl_regex functions. PHP has stated they are not going to support Perl6 RegEx. Real perl_regex compatible then huh.

    Some the Perl6 changes are pretty good for RegEx, but the complete drop of support for character clases just isn't a good thing (tm).

    My 2cents (who is glad at least Larry added the P5 modifier)

    --
    De Oppresso Liber
    1. Re:Yeah..more RegEx fragmentation by Anonymous Coward · · Score: 4, Insightful

      Perl 6 "reg"exs are not regular anymore (neither were Perl 5's of course...).
      Perl 6 is now more of a concise parser builder. As Jaime Zawinski has pointed out,
      regexes are not enough for real parsing, though people used Perl ones for ad-hoc parsing all the time.
      The sweeping syntax changes are an indicator of the Perl folk mutating Perl to be better at what people actually use if for - by the looks of things, they'll even stop calling them
      regexes soon, preferirng the term "rule"

  5. makes me glad I'm cutting back on Perl by g4dget · · Score: 5, Insightful

    I used to write a lot of Perl scripts and libraries. But I've been cutting back and using other scripting languages instead. Perl6 looks like it would not be a pleasant transition from Perl5; I don't want to have to learn a new, idiosyncratic language every major release. If some of the features in Perl6 turn out to be useful (like the new regex syntax), they will make it as libraries into other languages.

  6. Perl Rocks by Tsugumi · · Score: 4, Interesting
    There seem to be a lot of anti-perl flames, so until someone more intelligent, charismatic and pretty deigns to post, I may as well try to defend it...

    First - the myths, untruths etc that have sprung up so far.

    Perl6 is not backwards-compatible with Perl5 - uhm, yes it is. All your perl5 scripts will compile.

    Why not contribute to phython or [insert other language here] well, python will compile through Parrot too, so who cares? If you like Python, write in Python. I prefer $%&? syntax to whitespace-as-syntax, but each to their own, but that is the joy of Parrot. Think .Net CLR without the so-far unfounded feeling that M$ are doing something underhand and nasty that you can't put your finger on. Before someone replies with "Why not just use the CLR instead of Parrot"? bear in mind this has been done to death already. It's in the FAQ, read first, flame later.

    But why Perl? Okay, so it can be write-only. But this is only because of the flexibility, There Is More Than One Way To Do It. This includes obfuscated code, and plain unreadable alien transmissions. However - if you're writing code only you will ever see, then use the short-cuts. If you are writing code that needs to be maintained, then YOU the developer have the responsibility to ensure it is readable.

    Heck, you could always use english; - but this is perl, you can also code in Latin, or, uhm, Klingon.

    Perl is simply the most flexible language out there IMHO. If you're a sysadmin, you will have the Camel and the cookbook on your desk. Our entire environment is held together with Perl. Half the Internet is running on Perl. A dead language? Sheesh, Perl is dead, long live Perl.

    If there is anything that does worry me about perl6, it is that it is becomiung too powerful, and too encompassing - it is important that the balance is maintained whereby it remains the Swiss Army Knife of languages, that it remains as easy for the casual Perl programmer to keep getting their job done with simple scripts as it is to create large projects.

  7. Careful, Parrot != CLR by Ars-Fartsica · · Score: 4, Interesting
    PArrot will juice performance boosts at the sacrifice of built-in safety. This is by design. Dan Sugalski claimed as much in a Perl Review article - to paraphrase - "Parrot will execute the bytes sent to it by the native language compiler. IF the compiler writes improper Parrot, your app will crash.".

    He also goes on to note that the CLR could be a pluggable backend for Parrot to export to.

  8. Perl is beautiful by Ender+Ryan · · Score: 4, Insightful
    I simply don't understand what is up with all the Perl bashing going on here. I think it is mostly a sign of ignorance, because most of the negative comments about Perl are simply false.

    Many people say Perl is too big, has too many features, is too complicated, etc. This is simply false. Perl has tons of features, but, more than any other language I have ever used, you can use as little or as much of it as you want. You can pick up a Perl book and start writing Perl code in 15 minutes.

    Perl is ugly, hard to read, "write only", etc. This is complete horseshit, probably stemming from lack of experience with using Perl. Perl is very easy to write and read. Where I work, I have a co-worker who is not a programer. He learned Pascal years ago, but did not do any real coding until recently. Despite this, he can fairly easily read and modify my code. Yet, he can't read or modify my C/C++ code at all, and it's usually very readable, very clean, simple and concise.

    PHP/Python is better. A lot of people like to compare Perl to PHP and Python. Neither are "better", there really is no such thing. PHP is for web developers, and Perl can do everything PHP can do in nearly the exact same ways. Take a look at CPAN, there are so many Perl modules for use with Apache and web development in general that Perl is far, far more capable of a web programming language than PHP(IMO anyway). And Python, I've seen some absolutely fantastic stuff written in Python, but I hate Python, because it gives me a frickin headache. I cannot read/write Python, the lack of braces, indentation as syntax is just horrible on my eyes. Perhaps I'm slightly dyslexic or something, but when I'm looking at a page of Python code it all starts to swim and I cannot tell where each code block begins and ends.

    Now don't get me wrong, Perl isn't perfect. There are some things that bother me about Perl 5. # for comments, not bad but I really wish I could use C and C++ style comments in my Perl code. A bunch of #'s just look rather ugly. Threads, Perl 6 will have decent thread support from what I understand, I wish Perl 5 did, luckily for me everything I use Perl for I can fairly easily use multiple proceses instead, still would be nice though.

    I for one am looking forward to Perl 6. There will definately be a learning curve, but at least it will run most scripts without modification, will make upgrading much easier.

    Oh wait... this is /., it's easier to get modded up for bashing something... ok... Microsoft sucks! ;-)

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden