Michael G Schwern wrote:
On Sun, Jul 24, 2005 at 07:58:27PM -0400, John E. Malmberg wrote:
Has VMS.C changed any from Perl 5.8.7?
Between bleadperl and 5.8.7? Yes. Looks like mostly elimination of
5.005threads and consting and some of that char * casting you don't like.
You can get a copy of bleadperl via FTP, rsync is just more convenient.
ftp://ftp.linux.activestate.com/pub/staff/gsar/APC/perl-current/
I have a copy of bleadperl that I pulled down by rsync this morning
before I left to watch one of the local minor league teams grasp defeat
from the jaws of victory.
What I do not have locally is an unpacked copy of unmodified 5.8.6 or
5.8.7. The local copies on this system already have my ODS-5, UNIX, and
POSIX fixes, so I do not have a quick way to do a diff, and vms.c got
significant changes. And since then I have discovered a small buffer
highwater mark overrun in the original code. That fix is also only on
my work copy.
All of that reference stuff is on the work server where I did the changes.
I was just trying to see if I could get this fixed quickly, while I
worked on getting the current "blead" rsync to actually run using Posix
Threads.
Removing the consting is not a good thing unless the caller of the
routine is expecting the value to be modified. More consting is better
for optimizing compilers, particularly if their target is a CPU with
pipelining and lots of registers, which is the situation for Alpha and I64.
And that includes numeric constants, where a numeric location is
initialized at compile time, and never changed by the code. Putting a
const qualifier on it can make the resulting code more efficient.
Particularly if the variable has scope outside of the module it is
defined in.
-John
[EMAIL PROTECTED]
Personal Opinion Only
