jhi writes "After more than two long years of hard work, the perl5-porters is proud to announce Perl 5.8.0. The most important new features are enhanced Unicode and threads support, and the new I/O subsystem called PerlIO, but there are lots of new goodies, not to mention bazillion bug fixes.
The full announcement is available, and you can read what is new in 5.8.0, and if you like what you see, start installing.
Since this release has extensive support for non-Latin scripts, we also translated the announcement to Traditional Chinese (Big5-ETEN), Simplified Chinese (EUC-CN or GB2312), Japanese (EUC-JP), and Korean (EUC-KR) (by Autrijus Tang, Dan Kogai, and Jungshik Shin).
ftp://ftp.cpan.org/pub/CPAN/src/perl-5.8.0.tar.gz is the main URL to use, but of course any CPAN mirror will do once they catch up.
Share and Enjoy!
-- Jarkko Hietaniemi, on behalf of the Perl5 Porters"
5.8 didn't have a particularly easy birth. Thanks for seeing this project through.
You da man!
Re:Congrats and Thanks!
ask on 2002-07-19T17:13:02
Having just read thru perldelta, that looks like a huge body of work
I for one was wondering why it didn't get called 5.1.0.:-)
- askRe:Congrats and Thanks!
jdporter on 2002-07-19T19:52:30
Did you mean 5.10?
Re:Congrats and Thanks!
mckyj57 on 2002-07-25T16:46:05
Having just read thru perldelta, that looks like a huge body of work. Of course, now ever Perl author is scurrying off to check that their code still works under 5.8!;-) Great job on compatibility, for my very complex application (Interchange) worked flawlessly once all the modules were updated. This was the easiest of the major releases to update for -- and I have done from 5.003 all the way up.
I suddenly remembered that every time there's a new Perl release,
there's a whole slew of new documentation that makes me a better Perl
programmer. I decided to go hunting and diffing between
New PODs in 5.8.0:
perltooc.pod => perltootc.pod
Mysteriously renamed, or else it's a mistake. See, if you people used CVS instead of that OTHER version control software, these kinds of things would never happen. Seriously, I can't see what this will do for us other than to confuse people on IRC when they are pointed to documentation they don't have. But I don't read p5p, so I'm sure there's a logical reason.
Re:New PODs in 5.8.0
jordan on 2002-07-19T19:15:13
- perltooc.pod => perltootc.pod
Mysteriously renamed, or else it's a mistake. See, if you people used CVS instead of that OTHER version control software, these kinds of things would never happen. Seriously, I can't see what this will do for us other than to confuse people on IRC when they are pointed to documentation they don't have. But I don't read p5p, so I'm sure there's a logical reason.
To those who don't read p5p, all is revealed to those who use the great and powerful Google.
I think you meant that the name was changed from:
- perltootc.pod => perltooc.pld
Googling indicates this was done so as to not collide on the 8.3 filesystems with perltoot.pod.
I don't read p5p, but I sometimes browse the archives. It's fun!
Re:New PODs in 5.8.0
jdavidb on 2002-07-19T20:07:56
I think you meant that the name was changed from:
Yeah.
:) this was done so as to not collide on the 8.3 filesystems with perltoot.pod.
That's what I suspected, but no such changes seemed to have happened with any of the other long POD filenames, like perlthrtut.
I don't read p5p, but I sometimes browse the archives. It's fun!
Me too.
:) Re:New PODs in 5.8.0
schwern on 2002-07-19T20:27:36
>>this was done so as to not collide on the 8.3 filesystems with perltoot.pod.
>
>That's what I suspected, but no such changes seemed to have happened with any >of the other long POD filenames, like perlthrtut.
On 8.3 filesystems where the OS doesn't compensate (Windows can compensate), filenames are simply truncated to fit. So perltootc.pod becomes perltoot.pod and you have a problem, one will usually overwrite the other. So the problem isn't with filenames being to long, it's with long filenames truncating to the same short name.
perlthrtut.pod doesn't have this problem. If there was, say, a perlthrtenaciousd.pod, then there would be problems (8.3 filesystems would be the least of them).
Re:New PODs in 5.8.0
ziggy on 2002-07-19T21:55:50
Which mythical OSes and filesystems would these be, then?On 8.3 filesystems where the OS doesn't compensate[...]I've always thought that the whole 8.3 issue is a red herring; Perl can't run on MS-DOS, and MS-DOS is one of the very few 8.3 filesystems left on the planet.
Re:New PODs in 5.8.0
jhi on 2002-07-19T23:13:15
Perl 5.8.0 runs fine on DOS DJGPP. Read the perldelta.
Re:New PODs in 5.8.0
jhi on 2002-07-19T23:23:56
perldelta explains the perltooc.
If you didn't get perlsolaris, perldos, and so forth, something went wrong in your installation. I sure do get them. All README.$platform pods get installed as perl$platform.pod.
If the README.{cn,jp,ko,tw} mess up your terminal, change your terminal. If your terminal would not wimp out, you would see the the first lines of the pod telling the Eastern Asian encoding they are in. After that, you need to know how to read Chinese/Japanese/Korean. I sure don't
:-) Your CVS quip I almost resisted replying to, but I failed... CVS is in many ways technically inferior compared with Perforce, that's why Perforce is being used. If all you want is to read the changes, there's a mailing list, perl5-changes@perl.org, see either perlhack.pod or lists.perl.org.
Re:New PODs in 5.8.0
jdavidb on 2002-07-20T02:57:41
I hope my tone wasn't mistaken. There wasn't any criticism implied. Especially about CVS. In fact the CVS comment was a joke about CVS's abilities; the joke is that with CVS renaming a file is made so difficult that you would "never" have been able to rename the file.
:) BTW, I thought you would be sleeping the whole release cycle off, now.
:) Thanks for a job well done. Re:New PODs in 5.8.0
jhi on 2002-07-20T04:30:36
Well, in that particular feature CVS and Perforce suck equally.
Re:New PODs in 5.8.0
autrijus on 2002-07-22T05:17:49
Just for the record, in Perforce renaming is done like this:
p4 integate -i oldfile newfile
p4 delete oldfile
p4 submit
To rename directories, replace oldfile with oldpath/... and newfile to newpath/....
Whether that sucks or not is largely a amtter of personal preference.
:-) Re:New PODs in 5.8.0
nicholas on 2002-07-22T09:48:05
Just for the record, in Perforce renaming is done like this:
p4 integate -i oldfile newfile
p4 delete oldfile
p4 submit
You mean, like, you can rename a file without shell access onto the repository? Using just the client? Wow - that's so cool. Now the CVS developers know that it can be done, I'm sure they'll be tripping over themselves to implement it. [Not:-(] Re:New PODs in 5.8.0
jhi on 2002-07-22T23:49:39
Renames should be atomic.
