summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix example #4 in perlXStutIlya Zakharevich1997-01-161-4/+6
| | | | | | | | | | | 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>
* Re: documentation correction (i.e. patch) for perlsyn.podM.J.T. Guy1997-01-161-5/+2
| | | | | | | | | | | | | | | 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>
* [dummy merge]Chip Salzenberg1997-01-160-0/+0
|\ | | | | | | | | This merge exists so that the p5p version of the patch and the applied version are both in the history
| * Re: MakeMaker and 'make uninstall'Andreas Koenig1997-01-161-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | >>>>> 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>
* | Re: MakeMaker and 'make uninstall'Chip Salzenberg1997-01-161-3/+4
|/ | | | (this is the same change as commit 54bc88081d9355e4567ce06a1f7b14ac5a7a5334, but as applied)
* Re: xsubpp and Tk ==> segfaultIlya Zakharevich1997-01-161-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* low priority patchesPaul Marquess1997-01-163-45/+41
| | | | | | | 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>
* Avoid "uninitialized" warnings from POSIX::constant()Chip Salzenberg1997-01-161-1/+1
|
* Re: Uninitialized value in Carp.pm ? Gurusamy Sarathy1997-01-161-0/+1
| | | | private-msgid: <199701141815.NAA07960@aatma.engin.umich.edu>
* [dummy merge]Chip Salzenberg1997-01-160-0/+0
|\ | | | | | | | | This merge exists so that the p5p version of the patch and the applied version are both in the history
| * PATCH: AutoSplitGraham Barr1997-01-161-2/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | PATCH: AutoSplitChip Salzenberg1997-01-161-2/+21
|/ | | | (this is the same change as commit bb8fceff88bc3fe9e820d0761f1b0451a870ac65, but as applied)
* Re: FileCache::cacheout clobbers $_Roderick Schertler1997-01-162-2/+2
| | | | | | | 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>
* Refresh DB_File to 1.10Paul Marquess1997-01-162-9/+41
| | | | | | | this patch works around an incompatability that was introduced in Berkeley DB 1.86 p5p-msgid: <9701141247.AA21242@claudius.bfsec.bt.co.uk>
* Refresh Getopt::Long to 2.6Johan Vromans1997-01-161-6/+11
|
* Fix for fd leak in IO::File::new_tmpfileGraham Barr1997-01-162-6/+17
| | | | Signed-off-by: Graham Barr <gbarr@ti.com>
* patch for db-recno.tPaul Marquess1997-01-161-4/+28
| | | | | | | | | 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>
* [dummy merge]Chip Salzenberg1997-01-160-0/+0
|\ | | | | | | | | This merge exists so that the p5p version of the patch and the applied version are both in the history
| * Advice on TEST failureDominic Dunlop1997-01-161-4/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]>
* | Advice on TEST failureChip Salzenberg1997-01-161-5/+11
|/ | | | (this is the same change as commit 1ce51ea5e928b0e6fe3d33c847a736aaee083a49, but as applied)
* Make installperl quieter; only shared libraries need 0555Chip Salzenberg1997-01-161-9/+10
|
* Fix infinite loop for undef function in @SIG{__WARN__,__DIE__}Chip Salzenberg1997-01-161-27/+33
|
* Fail regex that starts with '{'Chip Salzenberg1997-01-161-1/+2
|
* [shell changes from patch from perl5.003_20 to perl5.003_21]Chip Salzenberg1997-01-165-22/+0
| | | | | | | | | | | | | | | 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
* [differences between cumulative patch application and perl5.003_20]perl-5.003_20Chip Salzenberg1997-01-080-0/+0
|\
| * New test: comp/proto.tGraham Barr1997-01-081-0/+379
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 ???
| * Patch: make hints files warn about db-recno failuresDominic Dunlop1997-01-084-12/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]>
| * Fix: empty @_ when calling empty-proto subs without parensGraham Barr1997-01-082-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * scalar caller doc fixRoderick Schertler1997-01-081-3/+4
| | | | | | | | | | | | | | 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>
| * doc patch: perldscRoderick Schertler1997-01-081-33/+34
| | | | | | | | | | | | | | | | 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>
| * doc patch for defined on perlfunc.podRoderick Schertler1997-01-081-0/+18
| | | | | | | | | | | | | | | | 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>
| * tiny doc patchesRoderick Schertler1997-01-082-2/+2
| | | | | | | | p5p-msgid: <23338.852394333@eeyore.ibcinc.com>
| * sigaction() problemsRoderick Schertler1997-01-082-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * Support libperl.so under FreeBSDOllivier Robert1997-01-082-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * plug for safe/opcode leaksDoug MacEachern1997-01-081-1/+1
| | | | | | | | | | | | | | CHECKOP was bailing out at compile time here without destroying the newly created/unscoped op. p5p-msgid: <199701072220.RAA02117@postman.osf.org>
* | [inseparable changes from patch from perl5.003_19 to perl5.003_20]Perl 5 Porters1997-01-0824-1447/+2189
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BUILD PROCESS Subject: Make Configure default to the first domain in /etc/resolv.conf From: Chip Salzenberg <chip@atlantic.net> Files: Configure Subject: Start all helper scripts with $startsh From: Chip Salzenberg <chip@atlantic.net> Files: Configure Subject: Support libperl.so under FreeBSD Date: Sun, 5 Jan 1997 22:41:49 +0100 From: Ollivier Robert <roberto@keltia.freenix.fr> Files: Configure Makefile.SH Msg-ID: <Mutt.19970105224149.roberto@keltia.freenix.fr> (applied based on p5p patch as commit b126116e5ae3d57fa007f8a42fd506805b35163b) CORE LANGUAGE CHANGES Subject: Rescind named closures From: Chip Salzenberg <chip@atlantic.net> Files: Makefile.SH op.c perly.c perly.c.diff perly.y pp_hot.c Subject: Fix: empty @_ when calling empty-proto subs without parens Date: Sat, 04 Jan 1997 10:29:04 +0000 From: Graham Barr <bodg@tiuk.ti.com> Files: perly.c perly.y (applied based on p5p patch as commit 3112f5de73952f91aa4e8005d9852dfddbcf0402) CORE PORTABILITY Subject: Configure/perl5/Compartmented Mode Workstation (fwd) Date: Mon, 06 Jan 1997 13:15:38 -0500 (EST) From: Andy Dougherty <doughera@fractal.phys.lafayette.edu> Files: Configure hints/dec_osf.sh private-msgid: <Pine.SOL.3.95.970106131505.1662C-100000@fractal.lafayette.ed Subject: Remove obsolete file "dl_os2.xs". From: Ilya Zakharevich <ilya@math.ohio-state.edu> Files: MANIFEST DOCUMENTATION Subject: tiny doc patches Date: Sat, 04 Jan 1997 11:12:13 -0500 From: Roderick Schertler <roderick@gate.net> Files: pod/perlapio.pod pod/perlnews.pod pod/perltoc.pod Msg-ID: <23338.852394333@eeyore.ibcinc.com> (applied based on p5p patch as commit b681178584626ba3718f1279845fd452317134c1) Subject: doc patch for defined on perlfunc.pod Date: 04 Jan 1997 21:28:30 -0500 From: Roderick Schertler <roderick@gate.net> Files: pod/perlfunc.pod Msg-ID: <pz91686ek1.fsf@eeyore.ibcinc.com> (applied based on p5p patch as commit 38e3adfd2e3d40b46e465482945c4f3de4bb50ef) Subject: doc patch: perldsc Date: 04 Jan 1997 21:25:58 -0500 From: Roderick Schertler <roderick@gate.net> Files: pod/perldsc.pod pod/perltoc.pod Msg-ID: <pzafqo6eo9.fsf@eeyore.ibcinc.com> (applied based on p5p patch as commit 4d42f92e5bf79556508016b7af91233b12e526eb) Subject: scalar caller doc fix Date: Mon, 06 Jan 1997 22:34:20 -0500 From: Roderick Schertler <roderick@gate.net> Files: pod/perlfunc.pod Msg-ID: <18245.852608060@eeyore.ibcinc.com> (applied based on p5p patch as commit 218104faecb0ec19e0f4f89e084959e757a5230f) Subject: Misc perlfunc updates From: Tom Christiansen <tchrist@mox.perl.com> Files: pod/perlfunc.pod pod/perltoc.pod LIBRARY AND EXTENSIONS Subject: sigaction() problems Date: Mon, 06 Jan 1997 15:42:04 -0500 From: Roderick Schertler <roderick@gate.net> Files: ext/POSIX/POSIX.pm ext/POSIX/POSIX.pod Msg-ID: <12808.852583324@eeyore.ibcinc.com> (applied based on p5p patch as commit 84e96f2bcc509ba2fb5d2c9608a30cc3cfdea41a) Subject: Fix importation of FileHandle methods; fix POSIX docs From: Chip Salzenberg <chip@atlantic.net> Files: ext/POSIX/POSIX.pm ext/POSIX/POSIX.pod lib/FileHandle.pm Subject: Patch: make hints files warn about db-recno failures Date: Sun, 5 Jan 1997 12:34:25 +0100 From: Dominic Dunlop <domo@slipper.ip.lu> Files: MANIFEST hints/aux.sh hints/broken-db.msg hints/freebsd.sh (applied based on p5p patch as commit 692df45da95e2b7d14c4560347ef4555bb40b621) OTHER CORE CHANGES Subject: Fix C< sub foo (&@); sub bar (&); foo {}, bar {}, bar {} > From: Chip Salzenberg <chip@atlantic.net> Files: perly.c perly.c.diff perly.y Subject: plug for safe/opcode leaks Date: Tue, 07 Jan 1997 17:20:46 -0500 From: Doug MacEachern <dougm@osf.org> Files: op.c Msg-ID: <199701072220.RAA02117@postman.osf.org> (applied based on p5p patch as commit 5cbfc2849d37f748a8facbcbf1c889c575943488) Subject: Fix Dynaloader failures with DProf Date: Mon, 06 Jan 1997 12:18:46 -0500 From: Gurusamy Sarathy <gsar@engin.umich.edu> Files: pp_hot.c private-msgid: <199701061718.MAA26909@aatma.engin.umich.edu> TESTS Subject: New test: comp/proto.t Date: Mon, 06 Jan 1997 09:13:03 +0000 From: Graham Barr <bodg@tiuk.ti.com> Files: MANIFEST t/comp/proto.t (applied based on p5p patch as commit 8c1635e65dc1b3900503d444e985e3f0e5601454)
* [dummy merge]Chip Salzenberg1997-01-080-0/+0
|\ | | | | | | | | This merge exists so that the p5p version of the patch and the applied version are both in the history
| * perlpod.pod possible patchesLarry W. Virden1997-01-081-20/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | I am discouraged because I have pretty much determined that a current incompatibility between Mail::Mailer, perl 5.003_19, and perlbug has resulted in a number of patchs and bug reports that I have sent over the past week appear to have disappeared into a sink hole. Anyways, I will attempt to do this by hand. The following is a patch to perlpod.pod to fix some things that are not formatting properly or which appear to be incomplete thoughts. p5p-msgid: <9701070756.AA1185@cas.org> Signed-off-by: x2487 <lvirden@cas.org>
* | perlpod.pod possible patchesChip Salzenberg1997-01-081-25/+27
|/ | | | (this is the same change as commit dd21fd8df4b58122c680bb0b8e543f75fb0fcd93, but as applied)
* [dummy merge]Chip Salzenberg1997-01-080-0/+0
|\ | | | | | | | | This merge exists so that the p5p version of the patch and the applied version are both in the history
| * Re: constant function inliningRoderick Schertler1997-01-082-1/+22
| | | | | | | | | | | | | | | | | | | | On Tue, 7 Jan 1997 18:21:28 +0000, Tim Bunce <Tim.Bunce@ig.co.uk> said: > > A few words about redefining [constant] functions would be worthwhile. Right, patch attached. p5p-msgid: <pzk9pp1b95.fsf@eeyore.ibcinc.com>
* | Re: constant function inliningChip Salzenberg1997-01-082-0/+21
|/ | | | (this is the same change as commit f0893e72a8aa916a77953ff2f1847494d1527fb8, but as applied)
* pod2html.PL patch (for 5.003-19)Fabien TASSIN1997-01-081-2/+3
| | | | | | | | | | | | I've just found 2 bugs: - incorrect order for tags in the header. - bad links if the filename contains one (or more) "_". Here is the patch : nexus:~perl/5.003-19/src/pod $ diff -c pod2html.PL.orig pod2html.PL p5p-msgid: <199701052347.AAA21297@solar5>
* File::Basename::dirname bugsRobin Barker1997-01-082-11/+26
| | | | private-msgid: <12393.9701071719@tempest.cise.npl.co.uk>
* More magic variable testsRoderick Schertler1997-01-082-7/+81
| | | | private-msgid: <7043.852565192@eeyore.ibcinc.com>
* Finish OP= warnings: none on ^=Chip Salzenberg1997-01-083-6/+6
|
* Fix $^X on systems that set it to Perl's basenameChip Salzenberg1997-01-082-19/+31
|
* [shell changes from patch from perl5.003_19 to perl5.003_20]Chip Salzenberg1997-01-084-188/+0
| | | | | | | | | | | | | | | | | | | | | Change from running these commands: # this file is obsolete rm -f ext/DynaLoader/dl_os2.xs # this file was renamed if test -f t/pragma/warn-global then mv t/pragma/warn-global t/pragma/warn-1global fi # new (and nearly new) tests must be executable touch t/comp/proto.t chmod +x t/comp/proto.t t/comp/use.t t/harness # ready to patch exit 0
* [differences between cumulative patch application and perl5.003_19]perl-5.003_19Chip Salzenberg1997-01-041-0/+0
|\
| * expanded flock() docsRoderick Schertler1997-01-041-8/+29
| | | | | | | | p5p-msgid: <4481.852337871@eeyore.ibcinc.com>
View Lorry Controller Status