Perl 5.8.0 Released
twoshortplanks writes "The latest version of Perl has been released, with new features such as better Unicode support, a new threads implementation, new IO layer support, and a whole plethora of bundled modules - plus a wonderful collection of regression tests and new documentation. The release notes and links to mirrors for download are on dev.perl.org." This is not a release candidate, it's the real thing, representing over two years of work by patch pumpkin holder Jarkko Hietaniemi and his merry band. Hugo van der Sanden is the new pumpking for perl 5.10.
patch pumpkin n. [Perl hackers] A notional token passed around among the members of a project. Possession of the patch pumpkin means one has the exclusive authority to make changes on the project's master source tree. The implicit assumption is that `pumpkin holder' status is temporary and rotates periodically among senior project members.
This term comes from the Perl development community, but has been sighted elsewhere. It derives from a stuffed-toy pumpkin that was passed around at a development shop years ago as the access control for a shared backup-tape drive.
I used to bulls-eye womp-rats in my pants
Perl is real programming language, and as for the readability aspect: Perl doesn't hold your hand. It's perfectly possible to write clear code in Perl. If I was to show you one of my scripts I'm sure anyone with basic programming knowledge would be able to understand it.
I'm no coward, but don't want to spend time creatying an account (and remembering it) right now.
perl-5.8.0 is now completely 11.00 and 10.20 HP C-ANSI-C and GNU gcc safe. There are more 'README' pieces about Oracle in README.hpux and DBD-Oracle's README's have been extended, and probably will be even more in the near future.
I've already made a pa-risc-2.0 gcc version prepared for Oracle available on https://www.beepz.com/personal/merijn for HP ITRC forum members, and I cannot promise, but a 10.20-pa-risc-1.1 version is planned for the near future.
BTW, I seldom read this forum.
Hello,
This is David Corbane the fink developer over at Apple.
I just wanted to give this warning, since the post above seem to be a well constructed trolling.
Fink is an apt-get (Debian) application for packagemanagement on Apple OS X platform. It works just like apt-get.
The three lines given above would not solve any of the issues, rather this would launch your workpod into a highly unstable state, since perl is used extensively within OS X.
Fink manages aplications outside the base installation of OS X and no third party package mangement should in any way bother with base OS X applications.
If you try the above, you will not be able to run any sort of cron applications (which are run by default and most of which involve perl scripts).
Also doing this removes some glue security bindings that are controlled by perl.
Please be aware that fink is only used outside the base system of OS X and the first two lines of the code above are deceptive and highly dangerious.
Please write me if you need any more info.
dmcorbane@corp.NOSPAM.apple.com
No. It was released today. You're thinking of the last Release Candidate which was released on Monday.
Check out camelbones and see if that scratches your itch.
Well, when Perl 6 is released (a while yet, I think) you'll find radical changes to the regexps. See Apocalypse 5 for more information.
Fork() is for creating a new process. The Perl 5.8.0 threads uses the threads pragma to spawn threads. But Perl doesn't share all data by default, so variables must be declared shareable via variable attributes( $variable : attribute). Artur Bergman wrote a good synopsis.
Which is better? Horses or cantelope melons?
HTML and Perl are two completely different things. HTML is a way of representing (textual) data, while Perl is a way of processing and/or creating data.
Stop the brainwash
For those with Perl already, the following is an easy way to download and upgrade:
perl -MCPAN -e 'install J/JH/JHI/perl-5.8.0.tar.gz'
Done. It's called BRL: Beautiful Report Language
- Beautiful: It is easy to write BRL code that is understandable and maintainable, appealing to a programmer's sense of aesthetics.
- Report: BRL is particularly suitable for constructing output that is a mix of static and dynamic content, e.g. web pages, e-mail messages. Its greatest strength is constructing output from SQL databases, though it is useful for many other tasks.
- Language: The full power of a general-purpose programming language is there, though you wouldn't know it from simple examples.
It is based on Scheme, which makes the syntax extremely simple yet powerful.Less is more !
- Perl's built-in sort should be about 20% faster on most lists
- More accurate number representation
- Lots of new modules and pragmas, including, for all C fans out there, one that implements C's switch.
And don't forget that this release adds Windows CE or "Windows Powered" or whatever MS are calling it now as a supported platform. Mobile Perl applications AHOY!Perl 6 is still reportedly about a year and a half away.
There have been periodic postings on slashdot of design documents describing how perl 6 will function. This is probably what you rememebr seeing.
Autovivification on access is seen as a bad feature, and it's intended that in perl6, there will only be autovivification on write. In other words if($hash{'index'}{'index'}==2) won't autovivify, but $hash{'index'}{'index'}=2 will. This is one of the design goals behind perl6, to fix those things which need fixing, but can't in perl5 because of backwards compatibility.
Erlang is a general-purpose programming language and runtime environment. Erlang has built-in support for concurrency, distribution and fault tolerance.
In other words, it's a small concurrent functional programming language developed by Ericsson after their experiments with Lisp and Prolog.
Although, you will not love it if have already poisoned by OO "snake oil"
If it's a case then try Dylan
Less is more !
Which is in this thread also.
( perl -MCPAN -e 'install perl-5.8.0.tar.gz' )
Yes, pseudohashes are deprecated in Perl 5.8.0. They will be removed completely in Perl 5.10.0.
how to invest, a novice's guide
Yes, it will -- starting with Perl 6.0. This is a complete rewrite that compiles to a bytecode called Parrot by default. You can compile Parrot bytecode into binary, or almost anything.
I, for one, welcome our new Antichrist overlord.
Thank you for your post. First, I'd like to say that I hoping you are who you claim to be. The fact that you're posting as an AC, and that google doesn't know about you, and that you're not listed as a fink developer at the fink project member list, and that no reference of you exists at the fink-devel archive gives me pause. Appologies if my skepticism turns out to be unwarranted. For the sake of this response, I will assume that you are not trolling and are who you claim to be.
That being the case, I'm afraid you've been misled by the comment that you initially responded to. That comment was posted by someone who extracted out a small section of a report that I sent to various mailing lists last night. The comment to which you responded has effectively deprived you of the relevant context surrounding the issue. My full report can be found at the archives for the three lists I sent it to:
- maco
sx@perl.org archive
- perl5-porters@perl.org
- fink
-devel@lists.sourceforge.net
To summarize the report, there is a dyld issue of perl undefined symbols under Mac OS X, when fink is installed, and when the user has manually upgraded to perl 5.8.0. This issue effectively renders the new perl installation unusable, in addition to many things that depend on perl.This is caused by fink setting PERL5LIB to /sw/lib/perl5 which contains one or more compiled XS modules. Since perl 5.8.0 is not binary compatible with any prior perl release all XS modules will have to be recompiled in order to not experience the show-stopping dyld issue.
At this moment in time there have been several replies. One was a reply from Max Horn, a senior developer at fink. And, another reply was a reply from Michael Schwern, quality assurance manager for perl. Both acknowledge this as an issue and further outline the cause of this as well as possible permanent solutions.
The steps outlined in the 'RESOLUTION' section of the report are sane and well tested. They do indeed correct the issue that the report details, and should absolutely not cause any peripheral problems.
I'd like to request that if you further reply, please also do so on one of the three lists mentioned above so we can keep everyone in the loop.
Thank you!
--- Fox