| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(this is the same change as commit 8fe3829d7944eb627ee5360e65ca8f7afe76886d, but as applied)
|
|
|
|
| |
Signed-off-by: Chip Salzenberg <chip@perl.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Fri, 4 Apr 1997, Chip Salzenberg wrote:
> According to Olaf Seibert:
> > In this report I am using the shared perl library, libperl.so.3.97.
> >
> > When building miniperl, it is linked with libperl.so.3.97 instead of
> > -lperl. This slightly confuses NetBSD's shared loader. When miniperl
> > is run from a directory where libperl.so.3.97 is not present, it
> > will fail to start.
> >
> > Fix: I think this should do it: Change in the Makefile
> > LLIBPERL= $(LIBPERL)
> > to
> > LLIBPERL= -lperl
>
> Porters? I'm a bit out of my depth with this, since I'm not sure
> of what's portable with dynamic loading and what isn't.
My paranoid fear is the following: Suppose you already have
perl5.003_97 installed somewhere and it has a corresponding
libperl.so.3.97 installed in the appropriate directory. Now suppose
you're rebuiding perl5.003_97 (e.g. to test a patch or whatever) and
your new ./perl is linked with the moral equivalent of
LD_LIBRARY_PATH=`pwd`; export LD_LIBRARY_PATH
cc -o perl -R $archlib -lperl [...]
Now, when you're down in the t/ library running your tests, and miniperl
gets called, which libperl.so.3.97 do you get -- the new one found via
LD_LIBRARY_PATH or the old one found via the -R directive?
(This is very similar to the shared libperl/debugging problem discussed in
the INSTALL file.)
I don't think any solution is bulletproof. I suspect that the suggested
change probably won't make matters any worse, but I'm wary at this stage
(gee, that's a suprise from me:-)
Instead, I think the following should probably be safe:
p5p-msgid: Pine.SOL.3.95q.970404124326.647K-100000@fractal.lafayette.edu
private-msgid: Pine.SOL.3.95q.970404124326.647K-100000@fractal.lafayette.ed
|
|
|
|
| |
p5p-msgid: 2848.860109823@eeyore.ibcinc.com
|
|
|
|
| |
private-msgid: 77724828@Armageddon.meb.uni-bonn.de
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The win32 make fails because it cannot find "camel.ico".
Even if I add a camel.ico stolen from elsewhere, the build
fails due to lack of "resource.h" referenced in "perl.rc"
(when using VC++ 2.0).
The following patch simply disables binding the icon resource
into perl.exe. (One can always associate a bare *.ico file
to any executable, so it's not like it *has* to be bound
into perl.exe when building it.)
p5p-msgid: 199704020608.BAA29538@aatma.engin.umich.edu
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CORE LANGUAGE CHANGES
Subject: Reenable but deprecate inherited AUTOLOAD for plain funcs
From: Chip Salzenberg <chip@perl.com>
Files: ext/DynaLoader/DynaLoader.pm gv.c lib/Text/ParseWords.pm pod/perldelta.pod pod/perldiag.pod t/op/method.t
CORE PORTABILITY
Subject: Win32 update
Date: Wed, 02 Apr 1997 01:08:09 -0500
From: Gurusamy Sarathy <gsar@engin.umich.edu>
Files: win32/VC-2.0/modules.mak win32/VC-2.0/perl.mak win32/VC- 2.0/perldll.mak win32/perl.mak
Msg-ID: 199704020608.BAA29538@aatma.engin.umich.edu
(applied based on p5p patch as commit 8d0ff1118aaee510902477e928a660803304346c)
DOCUMENTATION
Subject: Clean up some poddities, and make C<make html> work again
From: Chip Salzenberg <chip@perl.com>
Files: pod/Makefile pod/perldelta.pod pod/perldiag.pod pod/perlfaq8.pod pod/perlfunc.pod pod/perlop.pod pod/perltrap.pod
Subject: Eliminate pod warnings in libs
From: Chip Salzenberg <chip@perl.com>
Files: lib/CGI.pm lib/ExtUtils/Command.pm
LIBRARY AND EXTENSIONS
Subject: Eliminate warning in CGI.pm
From: Chip Salzenberg <chip@perl.com>
Files: lib/CGI.pm
OTHER CORE CHANGES
Subject: Introduce and use gv_fetchmethod_autoload()
From: Chip Salzenberg <chip@perl.com>
Files: global.sym gv.c pod/perlguts.pod proto.h universal.c
|
|\
| |
| |
| |
| | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Chip Salzenberg <chip@atlantic.net> wrote:
] According to Jim Avera:
] > Was there any resolution of the problem using SUPER:: with MakeMaker?
]
] Yes. Don't say "sub MY::foo {}"; say "package MY; sub foo {}".
] The current package is important for proper operation of SUPER::.
Thanks for your help. I appreciate it.
Here is a patch to fix the documentation (in 5.003_95).
p5p-msgid: 9704012235.AA07841@membrane.hal.com
|
|/
|
|
| |
(this is the same change as commit acce7d4e04d89207299003c3e80c69d50bc82069, but as applied)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Subject: Re: Strange headers from perldoc
On Mon, 31 Mar 1997 16:02:59 +0100, "M.J.T. Guy" <mjtg@cus.cam.ac.uk> said:
>
> When I go "perldoc CPAN" (in perl5.003_94 as it happens), the header
> lines come out as
>
> ::home::mjtg::pUser Contr::home::mjtg::perl5.003_94::lib::CPAN(3)
Here's a fix for that. It's just more heuristics, so it isn't perfect.
In a related vein, this still leaves
Getopt::Long(3pUser Contributed Perl DocumentatiGetopt::Long(3pm)
in the page header on my system. "User Contributed Perl Documentation"
is just too long. Would anybody mind replacing this with something
shorter? Say
Getopt::Long(3pm) User Perl Docs Getopt::Long(3pm)
or
Getopt::Long(3pm) Wankel Rotary Engine Getopt::Long(3pm)
or even
Getopt::Long(3pm) Getopt::Long(3pm)
I'm partial the last of these, myself, but I'd be happy with anything
less than about 20 characters. Patch happily supplied if nobody
objects.
p5p-msgid: pzn2ri9gto.fsf@eeyore.ibcinc.com
|
|\
| |
| |
| |
| | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Subject: Re: Patch for Benchmark.pm
In <9704011547.AA29906@toad.ig.co.uk>, Tim Bunce writes:
:Simple: calling functions in perl is expensive.
Yeah, I simply hadn't expected it to be *that* expensive.
:> - ? "sub { package $pack; my(\$_i)=$n; while (\$_i--){&\$c;} }"
:> + ? "sub { package $pack; my(\$_i)=$n; while (\$_i--){&\$c();} }"
:It's cheaper to _not_ add () so I'd recommend leaving it off.
I considered that, but felt it was more correct not to pass through the
parameters that were received. My new patch ducks it, by shifting @_
out before it gets there.
I also looked at having two caches for empty string/empty sub timings,
but was unable to get satisfactory results. I'll come back to that one,
but I don't think it is urgent for 5.004.
This patch is for the Benchmark.pm in _96: it repeats stuff from my
previous patch, but avoids stuff that was obsoleted by other changes
in _96.
p5p-msgid: 199704012231.XAA00225@crypt.compulink.co.uk
|
|/
|
|
| |
(this is the same change as commit 446534a1e286d6fde0fd79424865d3cf1291546b, but as applied)
|
|
|
|
|
|
| |
I've made a couple of (trivial) changes, in this compared to what was
distributed in _96. Patch available separately. Cape does not actually
enable wearer to fly.
|
|
|
|
|
|
|
| |
./perl -w t/lib/basename.t
gives some warnings.
p5p-msgid: 11173.9704011111@tempest.cise.npl.co.uk
|
|
|
|
|
|
|
| |
[editor's note: Chip credited Jens with the fix, but the message
doesn't have a patch. *shrug*]
p5p-msgid: Pine.SUN.3.91.970401153125.8053A-100000@holmenkollen.ifi.uio.no
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Subject: Fix for memory allocation on 'string'
Currently qq/a/ takes 2/3 of memory of "a" or 'a'. Test with
> env PERL_DEBUG_MSTATS=2 perl -e '$#a=10000; $a[$i] = qq// while $i++ <10000'
Memory allocation statistics after compilation: (buckets 8..8192)
17552 free: 0 9 24 16 16 3 1 2 1 0 1
43888 used: 0 119 232 176 16 5 3 10 0 0 1
Total sbrk(): 61800. Odd ends: sbrk(): 360, malloc(): 0 bytes.
Memory allocation statistics after execution: (buckets 8..65536)
17136 free: 0 121 21 15 16 3 1 0 1 0 1 0 0 0
515344 used: 0 10119 235 177 16 5 3 250 0 0 1 0 0 1
Total sbrk(): 532840. Odd ends: sbrk(): 360, malloc(): 0 bytes.
> env PERL_DEBUG_MSTATS=2 perl -e '$#a=10000; $a[$i] = "a" while $i++ <10000'
Memory allocation statistics after compilation: (buckets 8..8192)
17520 free: 0 9 23 16 16 3 1 2 1 0 1
43920 used: 0 119 233 176 16 5 3 10 0 0 1
Total sbrk(): 61800. Odd ends: sbrk(): 360, malloc(): 0 bytes.
Memory allocation statistics after execution: (buckets 8..65536)
17616 free: 0 121 4 15 16 3 1 1 1 0 1 0 0 0
713520 used: 0 10119 10236 177 16 5 3 131 0 0 1 0 0 1
Total sbrk(): 731496. Odd ends: sbrk(): 360, malloc(): 0 bytes.
The following patch fixes it:
p5p-msgid: 1997Apr1.113438.1913905@hmivax.humgen.upenn.edu
|
|/
|
|
| |
(this is the same change as commit 1bd69d1d0fa002def016e601cb71bfcd93600bd3, but as applied)
|
| |
|
| |
|
| |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
p5p-msgid: 199703261254.NAA10237@bergen.sn.no
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch contains various minor corrections and improvements to the
perl5.003_95 perlfunc POD text:
p5p-msgid: 199703262159.WAA17531@furubotn.sn.no
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Tom Christiansen wrote:
>>-w is removed from a lot of installed scripts, to
>>get rid of annoying warnings about legitimate code.
>
> Hm... I kinda think this is a bad idea. If there are too
> many warnings, something should be fixed. Historically,
> -w has at time been too noisy, and we've fixed it.
Right. Let's add a note somewhere (perlrun? perldelta? INSTALL?):
p5p-msgid: 199703251901.UAA15982@bombur2.uio.no
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The only place I found in all of perl 5.003095 that used the phrase
"Bare word" instead of "bareword" or "Bareword" was here:
p5p-msgid: 1997Mar27.130247.1911552@hmivax.humgen.upenn.edu
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
According to Chip Salzenberg:
> sprintf( tmpbuf1, "@F=split('%s');", splitstr );
Oh, that reminds me: Splits like perl -F"/" and perl -F",'" fail.
Of course, these might be considered user errors since they conflict
with the -F doc. However, the -F doc is incorrect anyway: It says that
the pattern will be quoted unless it is *surrounded* by the delimiter.
Perl uses quotes if it *starts* with the delimiter. Which is sometimes
better because it allows options: -F/foo/i.
Anyway, here is a fix. 1st part allows things like `-F/' according to
the doc. 2nd part, if you want it, (attempts to) allow -F",'" in
conflict with the doc, which implies -F",'" is an error.
BTW, note that it's too late to obey the current doc exactly.
That would forbid options (-F/foo/i) or expressions (-F'"" + $i++').
Currently, these work - and might be in use somewhere.
p5p-msgid: 199703252110.WAA16038@bombur2.uio.no
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On Mon, 24 Mar 1997 17:29:29 EST, Ken Fox wrote:
>Gurusamy Sarathy wrote:
>> >> Ken Fox wrote:
>> >> > The trouble with die happens in the longjmp to top_env ...
>> Testcase?
>
>Here's a good example that demonstrates both of my longjmp related
>problems. I'm using 5.003_94 on Solaris 2.5.1 (more info at
>bottom). I think that the perl_call_* API is being used correctly.
>
>---------------------------------------- BEGIN crash.c
>#include <EXTERN.h>
>#include <perl.h>
>static PerlInterpreter *my_perl;
>
>int call_sub(SV *sub)
>{
> int result = -1;
> int count;
> dSP;
>
> ENTER;
> SAVETMPS;
>
> PUSHMARK(sp);
> XPUSHs(sv_2mortal(newSViv(1)));
> PUTBACK;
> count = perl_call_sv(sub, G_SCALAR);
> SPAGAIN;
> if (count == 1) result = POPi;
> PUTBACK;
>
> FREETMPS;
> LEAVE;
> return result;
>}
>
>int main(int argc, char *argv[], char *envp[])
>{
> char *perl_args[] = { 0, "-e",
> "sub ok { $_[0] + 1; } sub crash { die 'crash\n'; }", 0 };
> my_perl = perl_alloc();
> perl_construct(my_perl);
> perl_parse(my_perl, 0, 3, perl_args, 0);
> perl_run(my_perl);
>
> /* this call works fine -- no error */
> printf(" sub ok: return = %d\n", call_sub((SV *)perl_get_cv("ok", FALSE)));
> /* this call eventually inokes die() which mangles the C stack with long jump */
> printf("sub crash: return = %d\n", call_sub((SV *)perl_get_cv("crash", FALSE)));
> /* this call is bogus but perl mangles the C stack with long jump trying to
> tell me about it. */
> printf(" sv_undef: return = %d\n", call_sub(&sv_undef));
> perl_destruct(my_perl);
> perl_free(my_perl);
> return 0;
>}
>---------------------------------------- END crash.c
>
>I don't expect either of these cases to trap the error and go on -- I'd
>have used G_EVAL to do that. What I do expect is that the C stack isn't
>scrambled when the error occurs -- that makes it virtually impossible to
>catch in a debugger:
Here's a patch for the above problem, which is symptomatic of larger
problems with perl_call_*() calls that happen outside perl_run() or
perl_parse(). Perl invokes longjmp() without checking if an associated
setjmp() exists. This is likely to cause coredumps galore for all the
perl embedfellows out there.
Note the size of this patch is mostly due to the conversion of the
DOCATCH() business to macros in order to give it a semblance of
order. It also does away with redundant calls to setjmp() (the
:restart branch in perl_call_sv()), and uses the C stack instead of
Copy().
I finished this patch yesterday, and gave it a day with my production
embeded app, so I'm fairly sure it don't have no bugs. :-)
p5p-msgid: 199703280031.TAA05711@aatma.engin.umich.edu
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the remote past, Roderick Schertler wrote:
> I posted a message to clpm asking for comments on Perl's new srand()
> default seed and Dean Inada replied. Here are his observations. I'm
> just a conduit, would somebody who knows what they're talking about
> please step in?
Sorry to be late:
I believe I'm the one who inserted the new code. I browse clpm very
infrequently - and skip large parts of p5p too, for that matter.
I'll freely admit it's not particularly well tuned. Since I don't know
much about randomness, anyone who do could do a better job, and I
suggested (on p5p) that someone might give it a try. My change was just
to grab a few more garbage values (pointer addresses, time & pid) and
multipliers that shold at least never produce worse results than the
original code.
The multipliers
- are prime numbers, just in case that makes a difference:-)
- have few 1 bits at the beginning in binary, to distribute values
varying in a small range "not worse than the old version did",
or something like that. I don't quite remember.
If you improve it, just remember:
- *every* input value (time, pid & so on) may vary within a very narrow
range and/or with a constant multiplier in some instances - or not
vary at all.
- cast things to a "large enough" unsigned and to avoid overflow
exception and/or warning on some compilers. And don't trust a
variable/function to be unsigned just because some standard says
that it should be.
>> Using ^ here seems pretty silly. It again invites identical seeds
>> every 1000001 microseconds. A much more natural seed would seem to be
>>
>> tv_sec*1000000 + tv_usec
>>
>> Which at least will never repeat on different ticks.
Unless int is small, which gives faster wraparound.
>> But (...) some round tv_usec to multiples of 10000 microseconds,
Ah, yes. That's why I didn't multiply tv_sec with anything.
Better fix: Replace 1000000 above with some uneven larger number.
>> it would still be useful to mix in a getpid().
Which I did.
>>> seed ^= ( ( 269 * (U32)getpid())
>>> ^ (26107 * (U32)&when)
>>> ^ (73819 * (U32)stack_sp));
>>
>> Since you're using primes here, why not use the addition operator from
>> the same field that the primes are in, which would generate a group
>> the size of the product of those primes for avoiding repetitions?
Fine. Someone said xor, but not with any arguments that I can rember.
>> Are you still using rand(3), rather than the better random(3)? If so,
>> there may be the additional issue that small changes in the seed tend
>> to produce small changes in the sequence. In that case, something
>> like seed*32769 (i.e. seed + (seed<<15)) may help. (though a prime
>> like 32771 might be better.)
INSTALL suggests -Drand=random -Dsrand=srandom if one wants larger
period. Which means the period could be anything. However,
#if RANDBITS > 32 ... #else #if RANDBITS > 16 ... #else ...
should allow us to tune this for the most common seed sizes.
Anyway, what should be used is a *real* hash function which spreads the
effect of every bit over a whole 1<<RANDBITS, so truncating to 32, 48 or
16 bits will all work. Multiplication with primes is not good enough,
because changes in high bits do not affect low bits of the seed.
However, I can't do that without checking some book, I don't know what
code to avoid which could cause recurring patterns instead...
Anyway, here is a starting point - slightly improved from your version:
[included code block applied as patch - ed]
Oh, also note:
Some time ago, Chip Salzenberg wrote:
>According to Fabien TASSIN:
>>> warning(1412): destination type of cast is too small to
>>> hold all pointers: truncation possible
>>> ^ (26107 * (U32)&when)
>>> ^
>>
>> this one is interesting for all 64bit OSs..
>
> It's on purpose. The value of "&when" is just a presumably large,
> difficult-to-predict value; converting it to U32 is the Right Thing,
> even on 64-bit machines.
Well,
(U32)(unsigned_with_same_size_as_pointers_t)&when
wouldn't hurt, if the latter type exists:-) And the same for
(U32)stack_sp, of course.
p5p-msgid: 199703302219.AAA20998@bombur2.uio.no
|
| | |
| | |
| | |
| | | |
p5p-msgid: 199703301922.VAA13509@furubotn.sn.no
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The declaration of safefree() in proto.h disagrees with the definition
in util.c.
p5p-msgid: 21338.859653381@eeyore.ibcinc.com
|
| | |
| | |
| | |
| | |
| | |
| | | |
Here are some fixes for the pod files.
p5p-msgid: <199703262353.PAA01819@macs.mxim.com>
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[editor's note: this commit was prepared manually so may differ in
minor ways to other inseperable changes commits]
CORE LANGUAGE CHANGES
Title: "Support $ENV{PERL5OPT}"
From: Chip Salzenberg
Files: perl.c pod/perldiag.pod pod/perldelta.pod pod/perlrun.pod
Title: "Implement void context, in which C<wantarray> is undef"
From: Chip Salzenberg
Files: cop.h doop.c dump.c global.sym gv.c op.c op.h perl.c
pod/perlcall.pod pod/perldelta.pod pod/perlfunc.pod
pod/perlguts.pod pod/perlsub.pod pp.c pp_ctl.c pp_hot.c
pp_sys.c proto.h
Title: "Don't look up &AUTOLOAD in @ISA when calling plain function"
From: Chip Salzenberg
Files: global.sym gv.c lib/Text/ParseWords.pm pod/perldelta.pod
pp_hot.c proto.h t/op/method.t
Title: "Allow closures to be constant subroutines"
From: Chip Salzenberg
Files: op.c
Title: "Make C<scalar(reverse)> mean C<scalar(reverse $_)>"
From: Chip Salzenberg
Files: pp.c
Title: "Fix lexical suicide from C<my $x = $x> in sub"
From: Chip Salzenberg
Files: op.c
Title: "Make "Unrecog. char." fatal, and update its doc"
From: Chip Salzenberg
Files: pod/perldiag.pod toke.c
CORE PORTABILITY
Title: "safefree() mismatch"
From: Roderick Schertler
Msg-ID: <21338.859653381@eeyore.ibcinc.com>
Date: Sat, 29 Mar 1997 11:36:21 -0500
Files: util.c
(applied based on p5p patch as commit id 9b9b466fb02dc96c81439bafbb3b2da55238cfd2)
Title: "Win32 update (seven patches)"
From: Gurusamy Sarathy and Nick Ing-Simmons
Files: EXTERN.h MANIFEST win32/Makefile win32/perl.mak
win32/perl.rc win32/perldll.mak win32/makedef.pl
win32/modules.mak win32/win32io.c win32/bin/pl2bat.bat
OTHER CORE CHANGES
Title: "Report PERL* environment variables in -V and perlbug"
From: Chip Salzenberg
Files: perl.c utils/perlbug.PL
Title: "Typo in perl.c: Printing NO_EMBED for perl -V"
From: Gisle Aas
Msg-ID: <199703301922.VAA13509@furubotn.sn.no>
Date: Sun, 30 Mar 1997 21:22:11 +0200
Files: perl.c
(applied based on p5p patch as commit id b6c639e4b1912ad03b9b10ba9518d96bd0a6cfaf)
Title: "Don't let C<$var = $var> untaint $var"
From: Chip Salzenberg
Files: pp_hot.c pp_sys.c sv.h t/op/taint.t
Title: "Fix autoviv bug in C<my $x; ++$x->{KEY}>"
From: Chip Salzenberg
Files: pp_hot.c
Title: "Re: 5.004's new srand() default seed"
From: Hallvard B Furuseth
Msg-ID: <199703302219.AAA20998@bombur2.uio.no>
Date: Mon, 31 Mar 1997 00:19:13 +0200 (MET DST)
Files: pp.c
(applied based on p5p patch as commit id d7d933a26349f945f93b2f0dbf85b773d8ca3219)
Title: "Re: embedded perl and top_env problem "
From: Gurusamy Sarathy
Msg-ID: <199703280031.TAA05711@aatma.engin.umich.edu>
Date: Thu, 27 Mar 1997 19:31:42 -0500
Files: gv.c interp.sym perl.c perl.h pp_ctl.c pp_sys.c scope.h util.c
(applied based on p5p patch as commit id f289f7d2518e7a8a82114282e774adf50fa6ce85)
Title: "Define and use new macro: boolSV()"
From: Tim Bunce
Files: gv.c lib/ExtUtils/typemap os2/os2.c pp.c pp_hot.c pp_sys.c
sv.c sv.h universal.c vms/vms.c
Title: "Re: strict @F"
From: Hallvard B Furuseth
Msg-ID: <199703252110.WAA16038@bombur2.uio.no>
Date: Tue, 25 Mar 1997 22:10:33 +0100 (MET)
Files: toke.c
(applied based on p5p patch as commit id dfd44a5c8c8dd4c001c595debfe73d011a96d844)
Title: "Try harder to identify errors at EOF"
From: Chip Salzenberg
Files: toke.c
Title: "Minor string change in toke.c: 'bareword'"
From: lvirden@cas.org
Msg-ID: <1997Mar27.130247.1911552@hmivax.humgen.upenn.edu>
Date: Thu, 27 Mar 1997 13:02:46 -0500 (EST)
Files: toke.c
(applied based on p5p patch as commit id 9b56c8f8085a9e773ad87c6b3c1d0b5e39dbc348)
Title: "Improve diagnostic on \r in program text"
From: Chip Salzenberg
Files: pod/perldiag.pod toke.c
Title: "Make Sock_size_t typedef work right"
From: Chip Salzenberg
Files: perl.h pp_sys.c
LIBRARY AND EXTENSIONS
Title: "New module constant.pm"
From: Tom Phoenix
Files: MANIFEST lib/constant.pm op.c pp.c t/pragma/constant.t
Title: "Remove chat2"
From: Chip Salzenberg
Files: MANIFEST lib/chat2.inter lib/chat2.pl
Title: "Include CGI.pm 2.32"
From: Chip Salzenberg
Files: MANIFEST eg/cgi/* lib/CGI.pm lib/CGI/Apache.pm
lib/CGI/Carp.pm lib/CGI/Fast.pm lib/CGI/Push.pm
lib/CGI/Switch.pm
UTILITIES
Title: "Tom C's Pod::Html and html tools, as of 30 March 97"
From: Chip Salzenberg
Files: MANIFEST installhtml lib/Pod/Html.pm pod/pod2html.PL
Title: "Fix path bugs in installhtml"
From: Robin Barker <rmb1@cise.npl.co.uk>
Msg-ID: <3180.9703270906@tempest.cise.npl.co.uk>
Date: Thu, 27 Mar 97 09:06:14 GMT
Files: installhtml
Title: "Make perlbug say that it's only for core Perl bugs"
From: Chip Salzenberg
Files: utils/perlbug.PL
DOCUMENTATION
Title: "Document autouse and constant; update diagnostics"
From: Chip Salzenberg
Files: pod/perldelta.pod
Title: "Suggest to upgraders that they try '-w' again"
From: Hallvard B Furuseth
Msg-ID: <199703251901.UAA15982@bombur2.uio.no>
Date: Tue, 25 Mar 1997 20:01:26 +0100 (MET)
Files: pod/perldelta.pod
(applied based on p5p patch as commit id 4176c059b9ba6b022e99c44270434a5c3e415b73)
Title: "Improve and update documentation of constant subs"
From: Tom Phoenix <rootbeer@teleport.com>
Msg-ID: <Pine.GSO.3.96.970331122546.14185C-100000@kelly.teleport.com>
Date: Mon, 31 Mar 1997 13:05:54 -0800 (PST)
Files: pod/perlsub.pod
Title: "Improve documentation of C<return>"
From: Chip Salzenberg
Files: pod/perlfunc.pod pod/perlsub.pod
Title: "perlfunc.pod patch"
From: Gisle Aas
Msg-ID: <199703262159.WAA17531@furubotn.sn.no>
Date: Wed, 26 Mar 1997 22:59:23 +0100
Files: pod/perlfunc.pod
(applied based on p5p patch as commit id 35a731fcbcd7860eb497d6598f3f77b8746319c4)
Title: "Use 'while (defined($x = <>)) {}', per <gnat@frii.com>"
From: Chip Salzenberg
Files: configpm lib/Term/Cap.pm perlsh pod/perlipc.pod pod/perlop.pod
pod/perlsub.pod pod/perlsyn.pod pod/perltrap.pod
pod/perlvar.pod win32/bin/search.bat
Title: "Document and test C<%> behavior with negative operands"
From: Chip Salzenberg
Files: pod/perlop.pod t/op/arith.t
Title: "Update docs on $]"
From: Chip Salzenberg
Files: pod/perlvar.pod
Title: "perlvar.pod patch"
From: Gisle Aas
Msg-ID: <199703261254.NAA10237@bergen.sn.no>
Date: Wed, 26 Mar 1997 13:54:00 +0100
Files: pod/perlvar.pod
(applied based on p5p patch as commit id 0aa182cb0caa3829032904b9754807b1b7418509)
Title: "Fix example of C<or> vs. C<||>"
From: Chip Salzenberg
Files: pod/perlsyn.pod
Title: "Pod usage and spelling patch"
From: Larry W. Virden
Files: pod/*.pod
Title: "Pod updates"
From: "Cary D. Renzema" <caryr@mxim.com>
Msg-ID: <199703262353.PAA01819@macs.mxim.com>
Date: Wed, 26 Mar 1997 15:53:22 -0800 (PST)
Files: pod/*.pod
(applied based on p5p patch as commit id 5695b28edc67a3f45e8a0f25755d07afef3660ac)
|
|\ \
| | |
| | |
| | |
| | | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| | |
| | |
| | |
| | |
| | |
| | | |
This didn't make it into 95.
p5p-msgid: 199703262305.PAA13121@ducks
|
|/ /
| |
| |
| | |
(this is the same change as commit 69cddaa00596e831c0492189df41823d75a1b069, but as applied)
|
|\ \
| | |
| | |
| | |
| | | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On March 25, I wrote:
> I'll try to take various comments into account and eliminate unnecessary
> markup in INSTALL. (I will, however, leave in what I consider to be
> necessary or useful markup.)
Here's a patch to bring you version 1.11 of the INSTALL file. This patch
is relative to the version in 5.003_95.
By far the biggest part of the patch is removing unnecessary markup in the
file. There actually wasn't all that much anyway, but most of it wasn't
necessary for clarity, so I just removed it. There are now just 13 uses
of C<> and B<>. (These too are debatable, but I have no interest in
debating them. I've already decided to keep them for now.)
I've included Chip's suggestion about 'splain and diagnostics.pm and added
a little more info about the pod format.
There are also some minor rewordings here and there, all aiming to enhance
clarity. I hope it didn't regress instead :-)
At this point, I don't see any reason to include a separate INSTALL.txt
version in the distribution. If we want to
mv INSTALL INSTALL.pod
I won't argue much against it.
p5p-msgid: Pine.SOL.3.95q.970326140905.10178A-100000@fractal.lafayette.edu
|
|/ /
| |
| |
| | |
(this is the same change as commit a5d126c22eb526701c899be27a05a7d0d93dff97, but as applied)
|
| |
| |
| |
| |
| |
| |
| | |
Seems that the C<.al> construct by itself causes pod2man to lose about half of
the line, which confuses the explanation of the argument in question:
p5p-msgid: rjray-9702272117.AA001223633@snakepit.ecte.uswc.uswest.com
|
|\ \
| | |
| | |
| | |
| | | |
This merge exists so that the p5p version of the patch and the applied
version are both in the history
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch is a cleanup for the Benchmark module. It documents all the
stuff that wasn't, including my recent patch to allow code references;
it removes the old perl-comment docs that duplicate the POD; it fixes
some minor bugs (mostly of the '$arg ||= $default' instead of
'$arg = $default unless defined $arg' variety) and generally tidies
things up a bit.
Let me know if any of this causes problems,
p5p-msgid: 199703291504.PAA01596@crypt.compulink.co.uk
Signed-off-by: Hugo van der Sanden <hv@crypt.compulink.co.uk>
|