Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Perl 7 is going to be Perl 5.32, mostly

perl.com

Post reply on HN
Print view View original

291–300 of 573 posts

Re: Perl 7 is going to be Perl 5.32, mostly

#291

Post by lizmat »

henearkr wrote: post #269

I had hope there would be a merging (with some compatibility layers and wrapper binaries) allowing to use Raku the same way Perl 5 was used (should not have been _that_ hard, just adding familiar options and special variables)... Now I'm seeing this goes in a total different direction.

Perhaps. Meanwhile, the most recent release of the Inline::Perl5 module of Raku allows one to have code blocks written in Perl inside Raku code, and vice-versa. And of course be able to use any CPAN module from Raku: https://modules.raku.org/dist/Inline::Perl5:cpan:NINE

Re: Perl 7 is going to be Perl 5.32, mostly

#292

Post by lizmat »

justin66 wrote: post #89
briandfoy wrote: post #56

Earlier quoted context omitted.

I already have Preparing for Perl 7 on LeanPub ( https://leanpub.com/preparing_for_perl7 )

I haven't touched perl in something like 15 years, but I can attest that Brian's (brian's? :) ) writings are useful.

brian d foy always insists on not using any capitalization or punctuation in their name.

Re: Perl 7 is going to be Perl 5.32, mostly

#293

Post by lizmat »

aduitsis wrote: post #183
Ovid wrote: post #155

As a short summary about Perl 7: If your Perl is old-school, that's OK. Use Perl 5 and we'll keeping supporting you. If you your Perl isn't old-school, use Perl 7 and get new features. If you're not sure, ask us and we'll hold your hand to help you understand. We're here to make sure you're OK.

Any chance Cor makes it into Perl 7?

I understand that to be the plan.

Re: Perl 7 is going to be Perl 5.32, mostly

#294

Post by btilly »

jlokier wrote: post #139
kungtotte wrote: post #122

Earlier quoted context omitted.

Perl 5.0 was released towards the end of 1994. Python 1.2 was released in 1995. The first public release of Java as 1.0 was in 1996. JavaScript appeared in 1995 as well, but the first ECMAScript standard didn't appear until 1997. First release of PHP was in 1995, same with Ruby. Perl pre-dates the initial release of all those languages and was already up to its fifth major version by that time.

To be honest Perl 5 isn't really like Perl 4. They are quite different languages - Perl 4 didn't have objects, and Perl 5 places heavy emphasis on them. Up to you to decide when you think it started, but I'd say the current language we think of as "Perl" started with the release of Perl 5.

Most Perl 4 runs under Perl 5, and most Perl 5 written in the early years did not place heavy emphasis on objects. When I started in Perl, it was common to write code in such a way that it would run under either because it might have to.

Today, objects are used heavily. And furthermore the way we write those classes has changed a lot since Moose and friends became popular. As a result most Perl code bases written in the last dozen years look less like early Perl 5 than early Perl 5 looked like Perl 4.

Perl 4 and Perl 5 are more of a continuum than different languages.

Re: Perl 7 is going to be Perl 5.32, mostly

#295

Post by notyourday »

btilly wrote: post #265
notyourday wrote: post #140

Earlier quoted context omitted.

> And on top of that, the sigils, refs, and `wantarray` systems means that figuring out what syntax you need to invoke something correctly is confusing mental overhead that you have to keep in mind for every function call That's just badly written libraries that exist in pretty much every ecosystem. By now it seems we have settled that after a couple of args the way to pass multiple arguments is via a hash.

I speak as someone who has programmed in Perl for over 20 years and at one point was the top poster on Perlmonks. The wantarray feature is a problem with Perl, and not libraries. It has nothing to do with how you pass your arguments, but rather how the data comes back. Every single function has to deal with the potential of context. Every choice you make has downsides. The choices made around wantarray tend to age po…

Return a reference to a hash. You are done.

Re: Perl 7 is going to be Perl 5.32, mostly

#296

Post by lizmat »

EricRiese wrote: post #255

You guys are just now getting to Perl 7? I'm already on Perl 11. http://perl11.org/

The Perl 11 initiative was started by some individuals in the Perl community, but it never gained much traction outside of the group around the ones that started it. It has been dormant for at least 8 years now.

Re: Perl 7 is going to be Perl 5.32, mostly

#297

Post by mrtweetyhack »

cutler wrote: post #153
OakNinja wrote: post #109

Developers in their forties wrote Perl. Developers in their thirties replaced Perl. Developers in their twenties say “What’s Perl?”

Yes and developers in their 50s retired in their mid-30s after making fortunes writing Perl.

Yes, they also retired writing assembly, C, Pascal, Fortran. Doesn't make it a good language

Re: Perl 7 is going to be Perl 5.32, mostly

#298

Post by mrtweetyhack »

sumanthvepa wrote: post #24

I was part of a team that wrote significant parts of Amazon's payment processing systems in Perl in the late 90s. I really loved the language. It's object system was so flexible and powerful. Once you understood how write idiomatic perl. It was a joy to use. I'm looking forward to trying out Perl 7.

Don't know anybody at Amazon but are they still using Perl or have they replaced it?

Re: Perl 7 is going to be Perl 5.32, mostly

#300

Post by yellowapple »

Scarblac wrote: post #248

Perl has these tiny neat features that I still miss in other languages. Like unless (opposite of if), and postfix syntax. print "It worked!\n" unless $error; print "Item: $_\n" foreach @items;

Ruby has some of these, too, thanks to its Perl heritage.

    puts "It worked!" unless error
    i = 0; puts "Item: #{i+=1}" while i
Unfortunately foreach didn't survive, but thankfully arrays have methods to achieve similar concision:

    items.each {|i| puts "Item: #{i}"}
Post reply on HN