| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes, dumpvar's dumpvalue routine gets a value it can't dump. The
simplest example to contrive is the one in this test: a tied hash that
can't tell you its keys. Until now, this would cause the whole dump to
abort as soon as it failed to dump one part.
With this commit, each stringify or unwind is inside an eval. Failed
stringifications or unwindings are replaced with a placeholder showing
the error.
unwind uses return to stop early, and rather than go through contortions
to wrap the eval in something that can then return 1 to test that eval
worked, I've just asserted that this code requires 5.14.0, which made $@
a much more reliable indicator of failure after eval.
|
| |
|
|
|
|
| |
I know we should really be fixing local($_), but that code
in scope.c is rather twisted, and I want to see this fix
in 5.16.
|
| | |
|
| |
|
|
|
|
| |
work if those objects are blessed into class names containing '='.
This is due to incorrect parsing through 'split' in dumpvar.pl line 165.
|
| |
|
|
|
|
|
| |
Remove all uses of $[, both reads and writes, from library code.
Test code (which must test behaviour of $[) is unchanged, as is the
actual implementation of $[. Uses in CPAN libraries are also untouched:
I've opened tickets at rt.cpan.org regarding them.
|
| |
|
|
|
|
|
|
|
|
| |
To silence spurious interpolation warnings, merely
create the stash entry for them. Ensure that the
re::Tie::Hash::NamedCapture module is always loaded
when we have created the tied hashes %+ and %-.
Revert change #30483, which is now unnecessary.
p4raw-link: @30483 on //depot/perl: 73f68b39467596f862aade4f4b46d6061aa98bd3
p4raw-id: //depot/perl@30490
|
| |
|
|
|
| |
to dump %+ and %-.
p4raw-id: //depot/perl@30483
|
| |
|
|
|
|
|
| |
McCamant's comment
Message-ID: <44B67921.6090901@iki.fi>
p4raw-id: //depot/perl@28567
|
| |
|
|
|
| |
Message-ID: <20060225101254.726.qmail@lists.develooper.com>
p4raw-id: //depot/perl@27342
|
| |
|
|
|
|
| |
From: "Michael G Schwern via RT" <perlbug-followup@perl.org>
Message-ID: <rt-3.0.11-6749-117055.16.4354496694007@perl.org>
p4raw-id: //depot/perl@25130
|
| |
|
|
|
| |
Message-ID: <20030919015858.GA22503@math.berkeley.edu>
p4raw-id: //depot/perl@21284
|
| |
|
|
|
| |
Message-ID: <Pine.LNX.4.44.0309102337150.2043-300000@tribal.metalab.unc.edu>
p4raw-id: //depot/perl@21173
|
| |
|
| |
p4raw-id: //depot/perl@21061
|
| |
|
|
|
| |
Message-Id: <1C49133C-DD91-11D7-8450-000393BCA0FC@ibiblio.org>
p4raw-id: //depot/perl@21010
|
| |
|
|
|
| |
Message-id: <4.3.2.7.2.20020319101746.00aa7aa0@shell2.webquarry.com>
p4raw-id: //depot/perl@15363
|
| |
|
|
|
| |
Message-id: <4.3.2.7.2.20020315153302.00bac420@shell2.webquarry.com>
p4raw-id: //depot/perl@15258
|
| |
|
|
|
| |
Message-ID: <20020213012042.25245.qmail@plover.com>
p4raw-id: //depot/perl@14670
|
| |
|
|
|
| |
Message-ID: <m3y9iot1jr.fsf@anima.de>
p4raw-id: //depot/perl@14402
|
| |
|
|
|
| |
Message-ID: <20010524050522.A18997@staff1.cso.uiuc.edu>
p4raw-id: //depot/perl@10191
|
| |
|
|
|
| |
<smurf@noris.de>); fix up duplicate code in Dumpvalue.pm
p4raw-id: //depot/perl@5839
|
| |
|
|
|
|
| |
Christiansen); make dumpvar.pl safe against non-glob entries
in stashes
p4raw-id: //depot/perl@5818
|
| |
|
|
|
| |
subroutines (from Ilya Zakharevich)
p4raw-id: //depot/perl@4975
|
| |
|
| |
p4raw-id: //depot/perl@3848
|
| |
|
|
|
| |
overloading
p4raw-id: //depot/perl@3570
|
| |
|
|
|
|
| |
Message-Id: <199807260128.VAA10543@monk.mps.ohio-state.edu>
Subject: [PATCH 5.004_76] better overloading
p4raw-id: //depot/maint-5.005/perl@1677
|
| |
|
|
|
|
| |
Message-Id: <199801040630.AA29298@metronet.com>
Subject: New patch for $^E==GetLastError() under Win32
p4raw-id: //depot/win32/perl@392
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
dumpvar.pl parses stringified references incorrectly when extrovert
class names are used. For example,
x bless {}, '=ARRAY('
will crash the debugger.
Patch (for 5.004_01 or 5.004_02) attached.
p5p-msgid: E0wwAjQ-0004l6-00@ursa.cus.cam.ac.uk
|
| |
|
|
|
| |
Turn off optional warnings
Eliminate $' to avoid runtime penalty
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
[editor's note: this commit combines approximate 4 months of furious
releases of Andy Dougherty and Larry Wall - see pod/perlhist.pod for
details. Andy notes that;
Alas neither my "Irwin AccuTrack" nor my DC 600A quarter-inch cartridge
backup tapes from that era seem to be readable anymore. I guess 13 years
exceeds the shelf life for that backup technology :-(.
]
|
| |
|
|
| |
[editor's note: the sparc executables have not been included,
and emacs backup files have been removed]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Subject: Configure now handles defaults much better
Subject: Configure now knows if config.sh was built on this machine
Subject: Configure now checks file existence more efficiently
Subject: Configure now handles stupid SCO csh
Configure has been heavily revised. Many of the tests that used
to simply force a decision now check that decision against the
previous value of the variable, and offer to let you change it.
The default now is to keep the old value, so that you don't lose
information from your previous run.
Because of this, it's now more important to know whether, in fact,
config.sh was produced on this machine and on this version of
the operating system. config.sh now contains a lastuname variable
which contains the output of uname -a. If this matches the current
output of uname -a, Configure defaults to including the old config.sh.
Otherwise not. If there is no valid config.sh, then Configure looks
defaults for the current architecture in the hints/ subdirectory
instead. The guesswork I've done in this section of code is
phenomenal, so you'll have to instruct me where I've misparsed
the output of uname (a problem in portability all of its own).
Subject: Configure now differentiates getgroups() type from getgid() type
Subject: Configure now figures out malloc ptr type
Subject: Configure now does better on sprintf()
Configure was assuming that the array of values returned from
getgroups was the same type as the gids returned by other system
calls. Unfortunately, reality set in. Likewise for malloc() and
sprintf(), which there is only one portable way to find out the return
value of: try it one way or the other, and see if it blows up.
Subject: C flags are now settable on a per-file basis
Subject: reduced maximum branch distance in eval.c
Certain compilers and/or optimizers get bozoed out by large
compilation units, or by large structures within those units.
Previously, you either had to change the compiler flags for all
the files, or do hairy editing in Makefile.SH and remake the Makefile,
necessitating a make depend. Now there is a script called cflags.SH
whose duty it is to return the proper CFLAGS for any given C file.
You can change the flags in just one spot now and they will be
immediately reflected in the next make (or even in the current
make, if one is running). Eventually I expect that any of the hints
files could modify cflags.SH, but I haven't done that yet.
The particular problem of long jump offsets in eval.c has been at
least partially alleviated by locating some of the labels in the
middle of the function instead of at the end. This still doesn't
help the poor Vax when you compile with -g, since it puts a jump
to the end of the function to allocate the stack frame and then
jumps back to the beginning of the function to execute it. For
now Vaxen will have to stick with -O or hand assemble eval.c and
teval.c with a -J switch.
Subject: fixed "Bad free" error
Subject: fixed debugger coredump on subroutines
Subject: regexec only allocated space for 9 subexpresssions
These are problems that were reported on the net and had unofficial
patches. Now they have official patches. Be sure to patch a
copy of your files without the unofficial patches, or the patch
program will get confused.
Subject: you may now use "die" and "caller" in a signal handler
Someone pointed out that using die to raise an exception out
of a signal handler trashed the expression value stack if the
exception was caught by eval. While fixing that, I also fixed
the longstanding problem that signal handlers didn't have a normal
call frame, which prevented the caller function from working.
Subject: fixed undefined environ problem
Subject: hopefully straightened out some of the Xenix mess
Subject: random cleanup in cpp namespace
Just keeping up with the current progress in non-standardization.
Subject: fixed failed fork to return undef as documented
The open function returns undef on failed implicit forks. The Book
assumed that the same was true of an explicit fork. I've made the
function behave like the Book says. It's a pity there's no way
to have an undefined value that returns -1 in a numeric context
but false in a boolean context...
Subject: generalized the yaccpar fixer some
Thanks to Andy Dougherty, perly.fixer now knows how to fix SVR3 2.2's
yaccpar code to do dynamic parse stack allocation. He also made it
easy for other people to insert their code there. Hooray!
Subject: find2perl sometimes needs to stat on the 2nd leg of a -o
Subject: find2perl didn't correctly handle switches with an argument of 0
In attempting to delay the lstat to the last moment, in case a filename
could be rejected on the basis of its name, find2perl neglected to
take into account the fact that control might pass to the 2nd half
of a -o without executing all of the 1st half, in particular without
executing the lstat.
find2perl was wisely removing leading zeroes from numbers that would
mistakenly be interpreted as octal numbers by Perl. Unfortunately,
this caused it to delete the number 0 entirely.
Subject: fixed dumpvar not to dump internal debugging info
Subject: substr($ENV{"PATH"},0,0) = "/foo:" didn't modify environment
Subject: $foo .= <BAR> could cause core dump for certain lengths of $foo
Subject: perl -de "print" wouldn't stop at the first statement
Random glitchy little things.
Subject: I'm at NetLabs now
I'm now working for NetLabs, Inc., and I hadn't changed my
address everywhere.
|
| |
|
|
| |
See patch #19.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In patch 13, there was a fix to make the VAR=value construct
in a command force interpretation by the shell. This was botched,
causing an argv list to be occasionally allocated with too small
a size. This problem is hidden on some machines because of
BSD malloc's semantics.
The lib/dumpvar.pl file was missing final 1; which made it
difficult to tell if it loaded right.
The lib/termcap.pl Tgetent subroutine didn't interpret ^x right
due to a missing ord().
In the section of the man page that gives hints for C programmers,
it falsely declared that you can't subscript array values. As of
patch 13, this statement is "inoperative".
The t/op.sleep test assumed that a sleep of 2 seconds would always
return a value of 2 seconds slept. Depending on the load and
the whimsey of the scheduler, it could actually sleep longer than
2 seconds upon occasion. It now allows sleeps of up to 10 seconds.
|
|
|
A few of the new features: (18 Oct)
* Perl can now handle binary data correctly and has functions to pack and unpack binary structures into arrays or lists. You can now do arbitrary ioctl functions.
* You can now pass things to subroutines by reference.
* Debugger enhancements.
* An array or associative array may now appear in a local() list.
* Array values may now be interpolated into strings.
* Subroutine names are now distinguished by prefixing with &. You can call subroutines without using do, and without passing any argument list at all.
* You can use the new -u switch to cause perl to dump core so that you can run undump and produce a binary executable image. Alternately you can use the "dump" operator after initializing any variables and such.
* You can now chop lists.
* Perl now uses /bin/csh to do filename globbing, if available. This means that filenames with spaces or other strangenesses work right.
* New functions: mkdir and rmdir, getppid, getpgrp and setpgrp, getpriority and setpriority, chroot, ioctl and fcntl, flock, readlink, lstat, rindex, pack and unpack, read, warn, dbmopen and dbmclose, dump, reverse, defined, undef.
|
