I've made another 5.8.x snapshot.

http://www.ccl4.org/~nick/P/perl-33218.tar.bz2
(or http://www.ccl4.org/~nick/P/perl-33218.tar.gz )

It's roughly what 5.8.9 is going to be, give or take breakage, late
interesting bug fixes, and resolution of some things that aren't quite there
yet (eg SysV::IPC vs C++ compilers, core headers vs Irix C compilers,
File::Spec vs MakeMaker on Win32, cflags.SH and -fstack-protector)

I'm curious how it fares on VMS, and which changes I've not integrated that I
should do to fix problems on VMS, Win32, or other platforms I don't understand
that well. In particular

1: Craig Berry says that the VMS diffs between 5.8.8 and 5.10 are 8000 lines.
   People have been busy (particularly John E. Malmberg)
   That's going to be too big to merge. In particular it (and 5.10) contains
   symlink support for VMS. I doubt that that should go in.
   But in turn John E. Malmberg made several VMS changes to File::Find,
   which I think related to symlinks, but I'm not sure. They're not in.
   Does it break things if they go in?

2: For some reason ext/B/t/lint.t, lib/Math/Complex.t and lib/Math/Trig.t
   have just blown up with Borland on Win32, despite seemingly being stable
   in 5.11 for a while. I hope that this is easy to fix

3: Jerry Hedden spotted that a change merged causes a gcc warning on Cygwin.
   I've yet tracked down what other change is not merged that would silence
   this. (It seemed more important to get everything else done, as it wasn't
   a build failure)

4: There are patches to Cygwin's README that I've not merged. I don't know
   what is relevant, and what relates to things that aren't merged


What else did I forget?

It's still Saturday, and I claim that I'm in time for this week's summary :-)

[And currently I have the last 65 changes in a row:
http://public.activestate.com/cgi-bin/perlbrowse?top=&show_recent=Show+Change+Log
Is there anyone (else) out there? :-)
]

Nicholas Clark

Reply via email to