| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The following script segfaults with _17 ():
#!./perl
my $x;
BEGIN {
$x = sub {print "in sub.\n"; undef $x};
sub X::DESTROY { print "Destroying.\n"}
bless $x, 'X';
}
# At this moment refcount of $x and &$x are 1 (we need a closure for this
# because of a sub leak).
&$x();
print "x: `$x'.\n";
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I propose the following patch for perl5.004. It automates the
generation of the documentation and is derived from the pioneer work
of Tom Christiansen, which was sub-documented, unfortunately.
It allows one to run 'roffitall' to generate the full manual and
table of contents, based on existing installed files only.
Next step: automate the maintainance of the roffitall file list, or
generate it automatically... Well, the current version should be OK
for 5.004.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
>>>>> "John" == John Stoffel <jfs@fluent.com> writes:
John> With a little bit of work I've gotten perl5.003_20 to compile
John> and pass all tests under Irix 6.4 on an Origin2000 box. The
John> trick is to realize that 'nm' output can't be parsed on this
John> machine. Here's the hints file to use for _21 when it's
John> released.
Chip et al,
I've also gotten it to compile and pass all tests under Irix 6.3 on an
O2, but I had to make some additions. I've put both hints files
below, which are the same except for the comments really, but in case
they need any changes, they can be made pretty easily now.
p5p-msgid: <199701132242.RAA14601@jfs.Fluent.COM>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Chip Salzenberg writes:
>
> It's all become so routine:
>
> file: $CPAN/authors/id/CHIPS/perl5.003_20.pat.gz
Below are latest os/2-related patches. **** Note the first chunk ****
It shows that under OS/2 4-argument select was writing over memory
(256 bites = 32 bytes) over what is typically 1-char malloc area.
Since an exception of the general rule is needed on linux and OS/2,
can we trust this rule at all? There may be zillions of obscure
little-endian systems where select sets all the bytes it cares about
instead of just the passed number.
If one wants a Configure test for this, here is the skeleton:
#include <stdlib.h>
#include <sys/select.h>
char buffer[81] = "01234567890123456789012345678901234567890123456789012345678901234567890123456789";
char buffer1[81] = "01234567890123456789012345678901234567890123456789012345678901234567890123456789";
int
main (int argc, char* argv[], char* envp[])
{
int i = 80;
buffer[0] = 2; /* stdout */
select(8, NULL, (fd_set *)buffer, NULL, NULL);
while (i > 0 && buffer1[i] == buffer[i]) i--;
printf("%i bytes overwritten.\n", i+1);
exit(0);
}
Enjoy,
Ilya
This patch does the following:
a) substitutes BSD (s)random instead of broken EMX's one;
b) removes rsignal from os2/os2.c since it it exported now;
c) defines `register' to none if better debugging is deemed necessary.
d) fixes broken pp_sselect.
p5p-msgid: <199701101102.GAA19051@monk.mps.ohio-state.edu>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Subject: Re: overloading broken in _20, or am I dense?
Randal Schwartz writes:
>
>
> This code works fine with _11, but breaks with _20. Did I mess
> something up? Or is something seriously broken in _20? (This is at
> the heart of making LWP work again.)
>
> #!/home/merlyn/test/bin/perl
>
> BEGIN {
> package A;
>
> sub as_string {
> shift->{"string"};
> }
> }
>
> BEGIN {
> package B;
> @ISA = qw(A);
> use overload ('""' => 'as_string', 'fallback' => 1);
>
> sub new {
> my $self = bless {}, shift;
> $self->{"string"} = shift;
> $self;
> }
> }
>
> $thing = new B "newbie";
> ## print $thing->as_string;
> print "$thing";
The patch below updates the following files:
gv.c
pp.c
t/op/overload.t
pod/perldiag.pod
lib/overload.pm
It fixes the above bug, another bug with autoloaded overloading
subroutines via inheritance (grok!), adds a way to do gv_findmeth
without creating import stubs (undocumented yet - give -1 as level),
and sneaks in a long-awaited ;-) feature *{\&subr}.
Final implementation of overloading does not use the above feature,
but I know a lot of uses for debugging. Anyway, feel free to remove
the first chunk of the patch if you feel offended by the above
feature.
Tested with _17.
Enjoy,
p5p-msgid: <199701131022.FAA22830@monk.mps.ohio-state.edu>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Subject: doc patches missing in _20
Here are a couple of the doc patches I sent to the list which didn't get
into _20. The first looks like an oversight (a related hunk got in),
but perhaps the second was left out intentionally, in anticipation of
changes in signal restart handling?
These are re-diffed against _20.
p5p-msgid: <102.852695733@eeyore.ibcinc.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Subject: Re: resetting pos broken in _20
On Mon, 13 Jan 1997 12:49:24 EST, Ilya Zakharevich wrote:
>Gurusamy Sarathy writes:
>> What's wrong with saying
>> C<pos $foo = length $foo> after /g fails, to get the behavior
>> you want?
>
>Since this has different semantics. You need to get `pos' before each
>match, and reset it after each failing match.
>
> /=/g; /;/g; /=/g; /;/g;
>
>may give you non-monotoneous movement of `pos' over the string, which
>is a bad thing.
Ahh, of course.
>But I still do not understand what you mean by "having pos at
>end". The bug was that position is reset at failing match, probably
>you have some other case in mind?
Never mind, I was missing the possibility of chaining //g matches
with the \G escape :-(
>I did not realize that pos was available at perl 4.?, bug-for-bug
>compatibility may be a reason if this was so for so many years...
The bug fix seems to make a lot sense (to me) now. \G was essentially
useless without the new "incompatiblity", eh?
Here's a pod update that documents current behavior in all the
places I could think of.
- Sarathy.
gsar@engin.umich.edu
p5p-msgid: <199701132013.PAA26606@aatma.engin.umich.edu>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Then again, your suggestion of having perldoc check $PERLDOC_PAGER first
shouldn't offend anybody.
p5p-msgid: <pzwwtoom8p.fsf@eeyore.ibcinc.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Subject: Re: Yet another perldoc option
I have added a new option to perldoc that just make it print the file
name of the module found. This enables me to say things like:
$ grep VERSION $(perldoc -l lwp)
which I find handy. This is also handy for various scripts that want
to reuse perldoc's module search algorithm. Perhaps this really
should have been made into a proper module. The 'l' was inspired by
grep(1).
p5p-msgid: <199610022200.AAA15334@furubotn.sn.no>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Subject: Re: perldoc problem?
> perldoc doesn't seem to work on absolute paths. Eg if you
> try
> perldoc /pdx/wmt/rtl/bin/analyze_netlist
> it waits and then complains. Wheras if you actually do
> cd /pdx/wmt/rtl/bin;perldoc analyze_netlist
> it works I've been waiting for this fix to happen for sometime.
This change to perldoc fixes the problem.
-Wayne
p5p-msgid: <199701082325.PAA04521@pdxlx008.intel.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
FreeBSD caerdonn.eurocontrol.fr 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Jan 6 10:35:39 MET 1997 roberto@caerdonn.eurocontrol.fr:/src/src/sys/compile/CAERDONN i386
lib/textwrap......ok
lib/timelocal.....ok
All tests successful.
u=0.421875 s=0.328125 cu=20.6484 cs=6.28125 files=142 tests=3412
Also please include the following patch in _21 (or 5.004 whichever is
planned):
p5p-msgid: <Mutt.19970108143747.roberto@caerdonn.eurocontrol.fr>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Subject: Patch: make hints files warn about db-recno failures (redux)
Sigh. Somehow, the patch for hints for machten.sh was missed out of my
submission, and so didn't make it into 5.003_20. Here you go:
p5p-msgid: <v03010d00aef92fba6aca@[194.51.248.78]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[George Hartlieb, a MLDBM user reported this problem in private mail.]
The following hypothetical construct:
for $k (keys %o) {
foo([$o{$k}]);
}
coredumps reliably when %o is a tied hash and the FETCH for the
value $o{$k} is substantial enough to cause a stack reallocation.
Patch against 3_19 attached.
- Sarathy.
gsar@engin.umich.edu
P.S: Whatever happened to the stack-of-stacks patch? Even the first
version of that patch would have eliminated this problem. There may
be many more places where such a fix may be necessary--it's impossible
to find them all. Please, let's atleast include a #ifdef-ed version
of that patch!
p5p-msgid: <199701100745.CAA13057@aatma.engin.umich.edu>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Subject: You can ++ and -- readonly integer scalars? (patch included)
I managed to find an illustration of the bug in a perl one-liner:
perl -e '*a = \100; $a++; print "$a\n"'
101
Perhaps that's been fixed in one of the beta releases which I'm not
running; or perhaps I'm the only one who finds that slightly incorrect.
If so, ignore the rest of this message.
You can modify readonly scalars using any of the pre/post
increment/decrement operators. Apparently, the only readonly checking is
done for cases like '100++'.
I managed to find the relevant code and add some SvREADONLY checks. It
now dies on the inc/dec of readonly scalars with the appropriate nasty
message. I just thought I'd share my patch.
Ashley Winters
p5p-msgid: <Pine.LNX.3.95.970110193330.11249D-100000@jql.accessone.com>
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
BUILD PROCESS
Subject: Make MachTen hints file warn about db-recno failures
Date: Wed, 8 Jan 1997 12:07:18 +0100
From: Dominic Dunlop <domo@slipper.ip.lu>
Files: hints/machten.sh
Msg-ID: <v03010d00aef92fba6aca@[194.51.248.78]>
(applied based on p5p patch as commit a4c70ab8da3ec1d87c83e5c617f4550814ec1724)
Subject: 5.003_20, FreeBSD 3.0 and minor patch
Date: Wed, 8 Jan 1997 14:37:47 +0100
From: Ollivier Robert <roberto@eurocontrol.fr>
Files: Configure
Msg-ID: <Mutt.19970108143747.roberto@caerdonn.eurocontrol.fr>
(applied based on p5p patch as commit 50e0d465254be88fb90ac23584812a529741b4b1)
CORE LANGUAGE CHANGES
Subject: Fix overloading via inherited autoloaded functions
Date: Mon, 13 Jan 1997 05:22:47 -0500 (EST)
From: Ilya Zakharevich <ilya@math.ohio-state.edu>
Files: gv.c lib/overload.pm pod/perldiag.pod t/pragma/overload.t
Msg-ID: <199701131022.FAA22830@monk.mps.ohio-state.edu>
(applied based on p5p patch as commit a9bc755754f0db5e848e65dfd2e63a96af50ffd4)
Subject: Method call fixes: Don't cache in alias, don't skip undef
From: Chip Salzenberg <chip@atlantic.net>
Files: global.sym gv.c gv.h hv.c op.c pod/perlguts.pod pod/perltoc.pod pp.c pp_ctl.c pp_hot.c proto.h scope.c sv.c t/op/method.t
Subject: Formats can be closures
From: Chip Salzenberg <chip@atlantic.net>
Files: cv.h op.c perly.c perly.c.diff perly.y pp_sys.c sv.h
Subject: Quote 'foo' in C<$x{-foo}>
From: Chip Salzenberg <chip@atlantic.net>
Files: toke.c
Subject: Forbid C< x->{y} > and C< x->[0] > under C<strict refs>
From: Chip Salzenberg <chip@atlantic.net>
Files: op.c pod/perldiag.pod t/pragma/strict-refs
Subject: Allow <=> to return undef when operands are not ordered
From: Chip Salzenberg <chip@perl.com>
Files: MANIFEST pp.c t/op/cmp.t
CORE PORTABILITY
Subject: Re: Perl 5.003_20: OS/2 patches
Date: Fri, 10 Jan 1997 06:02:16 -0500 (EST)
From: Ilya Zakharevich <ilya@math.ohio-state.edu>
Files: hints/os2.sh os2/Changes os2/os2.c os2/os2ish.h pp_sys.c
Msg-ID: <199701101102.GAA19051@monk.mps.ohio-state.edu>
(applied based on p5p patch as commit 9a3e71f668bd84b1cf53dd3ea10f588d59ecfebb)
Subject: VMS patches for _20
Date: Tue, 14 Jan 1997 17:34:43 -0500 (EST)
From: Charles Bailey <bailey@HMIVAX.HUMGEN.UPENN.EDU>
Files: configpm dosish.h os2/os2ish.h plan9/plan9ish.h proto.h t/pragma/strict.t t/pragma/subs.t t/pragma/warning.t toke.c unixish.h vms/Makefile vms/config.vms vms/descrip.mms vms/genconfig.pl vms/perly_c.vms vms/test.com vms/vmsish.h x2p/a2p.h x2p/str.c
private-msgid: <01IE7MGK7ULQ003K5M@hmivax.humgen.upenn.edu>
Subject: Irix 6.3 & 6.4 and perl5.003_20
Date: Mon, 13 Jan 1997 17:42:50 -0500 (EST)
From: John Stoffel <jfs@fluent.com>
Files: MANIFEST hints/irix_6_3.sh hints/irix_6_4.sh
Msg-ID: <199701132242.RAA14601@jfs.Fluent.COM>
(applied based on p5p patch as commit 8a1e91d771b51ae31eed1ac5944c63934213fb07)
Subject: Patch: MachTen hints, Configure
Date: Tue, 14 Jan 1997 13:43:13 +0100
From: Dominic Dunlop <domo@slipper.ip.lu>
Files: Configure hints/machten.sh
private-msgid: <v03010d00af0123a93670@[194.51.248.75]>
Subject: Rename aux.sh to aux_3.sh for MS-LOSS
From: Chip Salzenberg <chip@atlantic.net>
Files: MANIFEST hints/aux_3.sh
DOCUMENTATION
Subject: Full documentation generation patch
Date: Wed, 15 Jan 97 11:16:28 +0100
From: Raphael Manfredi <Raphael_Manfredi@grenoble.hp.com>
Files: MANIFEST pod/roffitall pod/rofftoc
Msg-ID: <15309.853323388@lyon.grenoble.hp.com>
(applied based on p5p patch as commit a3270a1d7469cab9221ab0050a0e6695bd0047d8)
Subject: Document use of pos() and /\G/
Date: Mon, 13 Jan 1997 15:13:12 -0500
From: Gurusamy Sarathy <gsar@engin.umich.edu>
Files: pod/perlfunc.pod pod/perlnews.pod pod/perlop.pod pod/perlre.pod pod/perltoc.pod pod/perltrap.pod
Msg-ID: <199701132013.PAA26606@aatma.engin.umich.edu>
(applied based on p5p patch as commit b2a07c1c241ec86f010fc0ea3bfa54c8ec28be90)
Subject: Document new closure warnings
From: Chip Salzenberg <chip@atlantic.net>
Files: op.c pod/perldiag.pod
Subject: Misc. doc patches missing in _20
Date: Tue, 07 Jan 1997 22:55:33 -0500
From: Roderick Schertler <roderick@gate.net>
Files: pod/perlsub.pod pod/perltoc.pod pod/perlvar.pod
Msg-ID: <102.852695733@eeyore.ibcinc.com>
(applied based on p5p patch as commit b88f04ff2985d0899964b90ae56789d88f6b353e)
LIBRARY AND EXTENSIONS
Subject: Localize info about filesystems being case-forgiving
From: Chip Salzenberg <chip@atlantic.net>
Files: lib/File/Basename.pm pod/checkpods.PL pod/pod2html.PL pod/pod2latex.PL pod/pod2man.PL pod/pod2text.PL utils/c2ph.PL utils/h2ph.PL utils/h2xs.PL utils/perlbug.PL utils/perldoc.PL utils/pl2pm.PL utils/splain.PL x2p/find2perl.PL x2p/s2p.PL
Subject: Eliminate warning from C<use overload>
From: Chip Salzenberg <chip@atlantic.net>
Files: lib/overload.pm
OTHER CORE CHANGES
Subject: Fix C< eval { my $x; eval '$x' } >
From: Chip Salzenberg <chip@atlantic.net>
Files: op.c t/op/misc.t
Subject: Don't warn if eval '' uses outer func's lexicals
From: Chip Salzenberg <chip@atlantic.net>
Files: op.c
Subject: Avoid memory wastage in wait(); make pidstatus global
From: Chip Salzenberg <chip@atlantic.net>
Files: global.sym interp.sym perl.c perl.h pp_sys.c
Subject: Forbid ++ and -- on readonly values
Date: Fri, 10 Jan 1997 19:47:16 -0800 (PST)
From: "John Q. Linux" <jql@accessone.com>
Files: pp.c pp_hot.c
Msg-ID: <Pine.LNX.3.95.970110193330.11249D-100000@jql.accessone.com>
(applied based on p5p patch as commit 74c80e585086695d5428ab316ca82fd6931aeabd)
Subject: Keep array from dying during foreach(@array)
From: Chip Salzenberg <chip@atlantic.net>
Files: cop.h pp_ctl.c
Subject: Fix C< $a="simple"; split /($a)/o >
From: Chip Salzenberg <chip@atlantic.net>
Files: pp.c t/op/misc.t
Subject: Fix for anon-lists with tied entries coredump
Date: Fri, 10 Jan 1997 02:45:11 -0500
From: Gurusamy Sarathy <gsar@engin.umich.edu>
Files: pp.c
Msg-ID: <199701100745.CAA13057@aatma.engin.umich.edu>
(applied based on p5p patch as commit d976ac8220f8890bb7663152c4870f60e8e018c8)
Subject: Don't set SVf_PADBUSY on immortal SVs
From: Chip Salzenberg <chip@atlantic.net>
Files: op.c
Subject: Patch for Object subroutines
Date: Tue, 7 Jan 1997 20:56:02 -0500 (EST)
From: Ilya Zakharevich <ilya@math.ohio-state.edu>
Files: cop.h
Msg-ID: <199701080156.UAA15366@monk.mps.ohio-state.edu>
(applied based on p5p patch as commit 174150afa5efdafc0e94a18211d3c9aa06b15cd9)
Subject: Use an SVt_PVLV to hold stacked OP pointers when debugging
From: Chip Salzenberg <chip@atlantic.net>
Files: pp.c pp_hot.c
Subject: Undo change that freed large pad vars
From: Chip Salzenberg <chip@atlantic.net>
Files: scope.c
TESTS
Subject: UNIVERSAL tests
From: Roderick Schertler <roderick@gate.net>
Files: MANIFEST t/op/universal.t
Subject: Test deletion of array during foreach
From: Jarkko Hietaniemi <jhi@alpha.hut.fi>
Files: t/op/misc.t
UTILITIES
Subject: Don't search for pod if path is already valid
Date: Wed, 08 Jan 1997 15:25:19 -0800
From: Wayne Scott <wscott@ichips.intel.com>
Files: utils/perldoc.PL
Msg-ID: <199701082325.PAA04521@pdxlx008.intel.com>
(applied based on p5p patch as commit 88f0eda82bb679b4e6445ccb17e18d0781c6a5da)
Subject: Yet another perldoc option
Date: Thu, 3 Oct 1996 00:00:35 +0200
From: Gisle Aas <aas@aas.no>
Files: utils/perldoc.PL
Msg-ID: <199610022200.AAA15334@furubotn.sn.no>
(applied based on p5p patch as commit a2333f3625faa17fb193cfa25c3d598cb59f105f)
Subject: Re: perldoc, temp files, async pagers
Date: 07 Jan 1997 22:54:14 -0500
From: Roderick Schertler <roderick@gate.net>
Files: utils/perldoc.PL
Msg-ID: <pzwwtoom8p.fsf@eeyore.ibcinc.com>
(applied based on p5p patch as commit 7c36043de26da560a0f7eb04f36d232762c0092c)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Subject: Example4 in perlXStut
The patch below makes Example 4 of perlXStut work. Thanks for Jeff for
suggestions.
Enjoy,
p5p-msgid: <199701050739.CAA11112@monk.mps.ohio-state.edu>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Robin Barker <rmb@cise.npl.co.uk> wrote
> Is this the right correction for perlsyn.pod regarding C<if BLOCK BLOCK> ?
>
> Is it too honest??
It doesn't seem sensible to fill up the pods with history like this.
In fact, perltrap has listed the feature as discontinued rather than
deprecated, since at least 5.002. It's been gone for well over a year
and nobody's complained. Let's just bury it. I suggest replacing
Robin's patch by
p5p-msgid: <E0vilLh-0000M6-00@ursa.cus.cam.ac.uk>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
>>>>> Hugo van der Sanden writes:
> I tried uninstalling a package today, the first time I've done so. The
> package was MailFolder0.03, and as far as I can see the uninstall:
> target in the Makefile was provided by MakeMaker. This does:
[...]
> and FULLEXT is defined as 'Mail'. The result was that most of the
> MailTools package was also removed.
Thanks for the report and _Sorry_.
Folks, I think, I have to deprecate the uninstall target. It was never
documented, it was never really clever, it just caused me a lot of
grief. I'd rather design a new solution from scratch.
If nobody objects, I'd recommend the following patch to
lib/ExtUtils/MM_Unix.pm. It makes use of the "nonono" switch of the
uninstall routine and will not uninstall anything.
Chip, can you sneak that in, please? Thanks!
p5p-msgid: <199701101243.NAA26400@anna.in-berlin.de>
|
| |/ / /
| | |
| | |
| | | |
(this is the same change as commit 54bc88081d9355e4567ce06a1f7b14ac5a7a5334, but as applied)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ilya Zakharevich writes:
>
> I recall that the reason why void code may be marked as XSRETURN(1) is
> that XS TUTORIAL recommended to mark XSUB as void if you manually put
It is not perlxstut, it is perlxs.
> in stack manipulation! I do not know why this horrible practice is
> blessed, but we need a workaround which would allow this mess, and
> would not make an XSUB
[Add: ] ... segfault if some Perl code was called in between.
As I found out, the only difference between an XSUB with a CODE:
section which is declared `void' and one which is declared "SV *" is
that the first one does not contain a line:
SV * RETVAL;
Is there any trouble if such a line is present?
If nobody will strongly object to it, I will remove an advice to
mark a CODE:-XSUBs as `void' from the POD(s).
I can also add a warning to xsubpp if a `void' XSUB sets ST(*). What
about it? (Warning will be issued only once per .xs .)
> Solution: Make the check for CODE section stricter: check for actuall
> occurence of "ST(" (with embedded spaces) before making the decision
> to XSRETURN(1).
The following patch is checked with Perl 3_17 and Tk (it checks for ST
at the LHS as an assignment):
Enjoy,
p5p-msgid: <199701080825.DAA15813@monk.mps.ohio-state.edu>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
this set of patches isn't super critical, but it does tidy a few things
up in anticipation of lexical warnings.
p5p-msgid: <9701081655.AA27349@claudius.bfsec.bt.co.uk>
|
| | | | |
|
| | | |
| | |
| | |
| | | |
private-msgid: <199701141815.NAA07960@aatma.engin.umich.edu>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Below is a patch which moves where AutoSplit splits a file. Currently AutoSplit
split when it sees a sub. This inhibits individual routines from having their
own use or require statements.
This patch causes AutoSplit to split at the last line starting with
a } before a sub.
The reason behind this is that I have a package which is a collection
of utility routines each requiring separate packages, as I am trying
to reduce what is loaded by autoloading the routines, it seems only
sensible to only 'use' packages when the routine which needs them it
loaded
p5p-msgid: <9603111010.AA29935@tiuk.ti.com>
|
| |/ / /
| | |
| | |
| | | |
(this is the same change as commit bb8fceff88bc3fe9e820d0761f1b0451a870ac65, but as applied)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This bug report was from last July, but the bug is still there.
FileCache.pm and cacheout.pl clobber $_.
p5p-msgid: <pz3ewb3189.fsf@eeyore.ibcinc.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
this patch works around an incompatability that was introduced in
Berkeley DB 1.86
p5p-msgid: <9701141247.AA21242@claudius.bfsec.bt.co.uk>
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Graham Barr <gbarr@ti.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Chip,
here is a patch for db-recno.t which makes it print a diagnostic
message when any of test 51,53 or 55 fail.
p5p-msgid: <9701121509.AA11147@claudius.bfsec.bt.co.uk>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
At 18:00 +0100 1997-01-09, Paul Marquess wrote:
>What are peoples views on this one. Should I simply write a diagnostic
>message to STDERR when test 51 fails? Some thing like this...
>
> base/cond.........ok
> lib/db-btree......ok
> lib/db-hash.......ok
> lib/db-recno...... not ok 51
> There is a known problem with older versions of Berkeley DB. You
> can ignore the errors if you're never going to use the broken
> functionality (recno databases with a modified bval), otherwise
> you'll have to upgrade your DB library or OS. If you feel like
> upgrading, the most recent version is 1.85. Check out
> http://www.bostic.com/db for more details.
Looks good to me. As of 5.003_20, hints/broken-db.msg is a shell scriptlet
that contains a similar (but not quite as useful) message for use by
Configure. It Would Be Nice if the same text (the same file?) were used in
both situations. But no big deal.
And, shortly afterwards, Tom Phoenix wrote:
>You're right. Who needs fine print? :-) What if 'make test' wrapped up
>with a message like this one?
>
> Failed 1 test, 96.55% okay.
> u=1.13 s=3.62 cu=60.49 cs=73.18 files=140 tests=3165
>
> ### Since not all tests were successful, you may want to run
> ### some tests individually to see the diagnostic messages,
> ### if any. See the INSTALL document's section on "make test".
That's a good idea, too, whether or not lib/db-recno blats something onto
the screen even when TEST is run without -v. Here's a patch which
implements it. (Well, with slightly different ordering.) I've also taken
the liberty of removing the RCS information from TEST, as it's meaningless
by now, of making the exit behaviour the same for one and for multiple
failures, and of trying to make the difference between "files" and "tests"
clearer. (This always confused me: I thought maybe "files" was the number
of files that got touched in the course of the tests.)
p5p-msgid: <v03010d01aefbaefcf3bc@[194.51.248.78]>
|
| |/ / /
| | |
| | |
| | | |
(this is the same change as commit 1ce51ea5e928b0e6fe3d33c847a736aaee083a49, but as applied)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Change from running these commands:
# this file is obsolete
rm -f hints/aux.sh
# new (and old) tests and scripts must be executable
touch t/op/cmp.t t/op/universal.t pod/rofftoc
chmod +x t/op/cmp.t t/op/universal.t pod/rofftoc pod/roffitall
# ready to patch
exit 0
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Chip Salzenberg wrote:
>
> According to Graham Barr:
> > BTW: I am working on a test (comp/proto.t) for this, and
> > prototypes in general.
>
> Thanks for telling me -- saved me some work.
OK, here is what I have done for comp/proto.t. More could probably
be added, but where do you stop.
I did find something weird though which caused the script to fail
just by changing the order of definitions ???
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Herewith some minor Configure and hints patches against 5.003_19:
1. Amend Configure so that MachTen's antediluvian test, which holds that
-1 is not an integer, does not bleat during non-blocking IO tests. (Tom
Christiansen posted a while back about several instances of this sort of
thing; this patch addresses the only one I can see. Are there
still others?)
2. Make hints files for A/UX, FreeBSD, and MachTen give notification
of the db-recno test failures caused by these systems' old db
libraries. This patch due mainly to Roderick Schertler, who implemented
a suggestion I made. I hope it's OK to put a shared stub in hints/. It
has the .shx extension so that it doesn't show up in Configure's list of
systems for which there are hints. It may be that the hints for some
version of IRIX need the same tweak, but I couldn't work out which one
from Martijn Koster's recent posting, and so left well enough alone.
p5p-msgid: <v03010d00aef53ac4d18a@[194.51.248.68]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Graham Barr wrote:
<snip>
> OK, so I thought that prototypes in Socket.pm (which is probably
> a good idea) could help here, but... guess what the following
> script outputs
>
> sub fred ()
> {
> warn join(" ",@_);
> }
>
> fred;
> @_ = qw(a b c);
> &fred;
> fred;
> __END__
>
> It outputs ...
>
> Warning: something's wrong at yyy line 3.
> a b c at yyy line 3.
> a b c at yyy line 3.
>
> OK I can belive the second one as it has the & style call (which
> the pod states overrides prototypes) but I was very amazed at
> the last call.
>
> Is this a bug ?? I think so as the pod suggests that a sub defined
> as
>
> sub mytime ();
>
> and a statement such as
>
> mytime +2;
>
> will by the same as
>
> mytime() + 2
>
> but this is not the case, it seems it would be
>
> &mytime(@_) + 2
>
OK, here is a patch which fixes this. It requires a modification
to perly.y and perly.c (I cannot re-generate perly.c here
but it is a simple fix)
it chamges the output of the above script to
Warning: something's wrong at yyy line 3.
Warning: something's wrong at yyy line 3.
a b c at yyy line 3.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The second bit is due to Tom Phoenix, I stuck it in since I was in there
already.
p5p-msgid: <18245.852608060@eeyore.ibcinc.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Mostly just fixed a couple of bracing and sorting problems, plus a little
bit of cosmetics. Dunno how this bitrot seeps in.
p5p-msgid: <1623.846039492@jinete.perl.com>
private-msgid: <pzafqo6eo9.fsf@eeyore.ibcinc.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I keep getting this question, so I thought I'd doc it. I still wonder
whether it's a bug. How does this sound, Larry?
p5p-msgid: <1509.846038569@jinete.perl.com>
private-msgid: <pz91686ek1.fsf@eeyore.ibcinc.com>
|
| | | | |
| | | |
| | | |
| | | | |
p5p-msgid: <23338.852394333@eeyore.ibcinc.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Working out an example of non-restarting syscalls I found three
problems.
- sigaction warns if there are no flags in the SigAction structure. I
think the SigAction constructor should treat the SigSet and flags
args as optional. Minimalist patch appended.
$ ./perl -MPOSIX=:signal_h -we '
sigaction 2, new POSIX::SigAction sub { }'
Use of uninitialized value at -e line 1.
$ ./perl -MPOSIX=:signal_h -we '
sigaction 2, new POSIX::SigAction sub { }, undef, 0'
$ _
- POSIX::constant warns on an arg-less macro.
$ ./perl -MPOSIX=:signal_h -lwe 'print SIGALRM'
Use of uninitialized value at /usr/local/lib/perl5/POSIX.pm line 197.
14
$ ./perl -MPOSIX=:signal_h -lwe 'print SIGALRM(0)'
14
$ _
- sigaction doesn't actually work.
$ ./perl -MPOSIX=:signal_h -we '
sigaction SIGALRM(0),
new POSIX::SigAction sub { die "alarm\n" }, undef, 0;
kill "ALRM", $$'
SIGALRM handler "CODE(0x223970)" not defined.
$ _
p5p-msgid: <12808.852583324@eeyore.ibcinc.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Subject: Re: 5.003_18 + shared libperl + FreeBSD 3.0-CURRENT
According to Andy Dougherty:
> There's a section in Configure to add such things. Edit Configure and
> look for a section like
After many tests, here are the two patches that enable use of either shared
or static libperl. Please everyone verify that I didn't broke anything
(especially with the second patch in Makefile.SH)...
Differences between NetBSD & FreeBSD surprise me because we're supposed to
have almost the same ld/ld.so...
p5p-msgid: <Mutt.19970105224149.roberto@keltia.freenix.fr>
|
