| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
p4raw-id: //depot/perl@10138
|
|
|
|
|
|
|
| |
Message-ID: <Pine.LNX.4.33.0105160858480.2488-100000@lapaki.jach.hawaii.edu>
Add pod2latex to utils.lst.
p4raw-id: //depot/perl@10137
|
|
|
|
|
| |
Message-ID: <20010516130443.E1516273@linguist.thayer.dartmouth.edu>
p4raw-id: //depot/perl@10136
|
|
|
|
|
| |
Message-ID: <20010516180208.A6458@netthink.co.uk>
p4raw-id: //depot/perl@10135
|
|
|
|
|
|
|
|
|
| |
v5.7.1 +DEVEL10104 on i586-linux 2.2.16-22 (UNINST
Message-ID: <3B0146AA.2839.17BFDA6@localhost>
Test case for #10128.
p4raw-id: //depot/perl@10134
|
|
|
| |
p4raw-id: //depot/perl@10133
|
|
|
| |
p4raw-id: //depot/perl@10132
|
|
|
| |
p4raw-id: //depot/perl@10131
|
|
|
| |
p4raw-id: //depot/perl@10130
|
|
|
|
|
| |
Message-ID: <20010516155755.A4728@netthink.co.uk>
p4raw-id: //depot/perl@10129
|
|
|
|
|
|
|
|
|
| |
v5.7.1 +DEVEL10104 on i586-linux 2.2.16-22 (UNINST
Message-ID: <3B0159C9.1905.1C6AEF9@localhost>
Fix PERL_Y2KWARN test to check before rather than after appending.
p4raw-id: //depot/perl@10128
|
|
|
| |
p4raw-id: //depot/perl@10127
|
|
|
| |
p4raw-id: //depot/perl@10125
|
|
|
| |
p4raw-id: //depot/perl@10124
|
|
|
| |
p4raw-id: //depot/perl@10123
|
|
|
| |
p4raw-id: //depot/perl@10122
|
|
|
|
|
| |
from Takis Psarogiannakopoulos.
p4raw-id: //depot/perl@10121
|
|
|
|
|
| |
Message-ID: <20010515190935.A27268@penderel>
p4raw-id: //depot/perl@10120
|
|
|
|
|
| |
than truncating, would have saved at least my confusion.
p4raw-id: //depot/perl@10119
|
|
|
|
|
| |
Message-ID: <3AFC2AE5.5E787E54@rowman.com>
p4raw-id: //depot/perl@10118
|
|
|
|
|
| |
Message-ID: <20010513202036.A21896@netthink.co.uk>
p4raw-id: //depot/perl@10117
|
|
|
| |
p4raw-id: //depot/perl@10116
|
|
|
|
|
|
|
| |
fully cured, there were remnants of $CONFIG when
$CONFIGDOTSH was expected. Now renamed to PERL_CONFIG_SH
to avoid future conflicts.
p4raw-id: //depot/perl@10113
|
|
|
| |
p4raw-id: //depot/perl@10112
|
|
|
|
|
| |
Message-ID: <20010514222708.A22963@penderel>
p4raw-id: //depot/perl@10110
|
|
|
|
|
| |
Message-ID: <20010514221643.A22437@penderel>
p4raw-id: //depot/perl@10109
|
|
|
|
|
| |
Message-ID: <20010514220344.A20643@penderel>
p4raw-id: //depot/perl@10108
|
|
|
|
|
| |
Message-ID: <20010514221007.A21118@penderel>
p4raw-id: //depot/perl@10107
|
|
|
|
|
| |
collation magic.
p4raw-id: //depot/perl@10106
|
|
|
| |
p4raw-id: //depot/perl@10105
|
|
|
| |
p4raw-id: //depot/perl@10104
|
|
|
|
|
|
|
|
|
|
| |
PL_last_in_gv may not be a GV if it was a stale filehandle (fix for
bug ID 20010514.027)
p4raw-link: @10100 on //depot/maint-5.6/perl: 5244397c028305e17ca4ad7e80cf900323dbeb8b
p4raw-id: //depot/perl@10103
p4raw-integrated: from //depot/maint-5.6/perl@10102 'merge in' mg.c
(@9288..) pp_ctl.c (@9584..)
|
|
|
| |
p4raw-id: //depot/perl@10102
|
|
|
|
|
| |
Message-ID: <20010514093859.A1479715@linguist.thayer.dartmouth.edu>
p4raw-id: //depot/perl@10101
|
|
|
|
|
|
|
|
| |
accessors only with one argument, an array or a hash reference,
sets the underlying array or hash. This mirrors nicely also
the usage in the constructor.
From Bernd Sokolowsky <ulmo@garozzo.franken.de>, via Damian Conway.
p4raw-id: //depot/perl@10099
|
|
|
|
|
| |
process shebang, as pointed out by Sarathy in #10091.
p4raw-id: //depot/perl@10098
|
|
|
|
|
|
|
|
| |
Message-ID: <20010512163627.A5522@netthink.co.uk>
with some additions salvaged from Todo and Todo-5.6 before
retiring them.
p4raw-id: //depot/perl@10097
|
|
|
|
|
| |
Message-Id: <02453af6b23e63-gin@mo.msk.ru>
p4raw-id: //depot/perl@10096
|
|
|
|
|
| |
Message-Id: <200105071535.f47FZvf27235@xerxes.courtesan.com>
p4raw-id: //depot/perl@10095
|
|
|
|
|
|
| |
Subject: [PATCH bleadperl Pod::Text] avoid overquoting [Was: rand(0) is rand(1)]
Message-ID: <20010512012810.B26358@jester.slaysys.com>
p4raw-id: //depot/perl@10094
|
|
|
|
|
| |
Message-Id: <E14ye49-0006Fn-00@libra.cus.cam.ac.uk>
p4raw-id: //depot/perl@10093
|
|
|
| |
p4raw-id: //depot/perl@10092
|
|
|
| |
p4raw-id: //depot/perl@10090
|
|
|
|
|
| |
Message-ID: <Pine.LNX.4.21.0105111131540.1804-100000@marmot.rim.canoe.ca>
p4raw-id: //depot/perl@10089
|
|
|
|
|
| |
Message-ID: <Pine.LNX.4.21.0105111647240.4478-100000@mako.covalent.net>
p4raw-id: //depot/perl@10088
|
|
|
|
|
| |
Message-ID: <Pine.OSF.4.10.10105111736190.73589-100000@aspara.forte.com>
p4raw-id: //depot/perl@10087
|
|
|
| |
p4raw-id: //depot/perl@10086
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the 'physical vs logical' range scheme:
\xAA-\xCC is a native physical range, you want that range of
codepoints in your native encoding. In EBCDIC the codepoints
in the gaps (between i-j and r-s) should be included.
\x{AA}-\x{CC} is a physical Unicode range, you want that range of
codepoints in Unicode.
a-z is a logical range, you want that range of 'logical' codepoints
in your native encoding. In EBCDIC the codepoints in the gaps
(between i-j and r-s) should not be included.
Mixed cases (a-\xAA, etc) should either be errors, or maybe
the 'logical' endpoints should be converted to native/Unicode
codepoints, and the range handled as a physical range.
'Logical endpoints' are to be recognized only in the A-Z, a-z,
and 0-9 ranges. Probably a warning should be given for mixed
cases like A-z or a-9 (since such expressions are encoding
dependent), with a recommendation to use physical ranges.
p4raw-id: //depot/perl@10085
|
|
|
|
|
|
| |
both before and after the testing so that we always
have a clean slate to work with.
p4raw-id: //depot/perl@10084
|
|
|
|
|
| |
Message-ID: <20010511143628.24225.qmail@web10402.mail.yahoo.com>
p4raw-id: //depot/perl@10083
|