summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* configpm: Fix broken linksKarl Williamson2011-05-181-2/+2
|
* perlsub.pod: Fix broken linkKarl Williamson2011-05-181-1/+1
|
* perlguts: Link to internal doesn't need pod nameKarl Williamson2011-05-181-1/+1
|
* perlfaq9: Add links to man pagesKarl Williamson2011-05-181-1/+1
|
* perlfaq8: Add links to man pagesKarl Williamson2011-05-181-4/+4
|
* perlebcdic.pod: Add man page section number to linkKarl Williamson2011-05-181-1/+1
|
* perldata.pod: Fix broken linkKarl Williamson2011-05-181-2/+2
|
* mathoms.c: pod: fix broken linkKarl Williamson2011-05-181-1/+1
|
* vmsish.pm: Fix broken linkKarl Williamson2011-05-181-2/+2
|
* Attribute-Handlers: Fix broken linkKarl Williamson2011-05-181-3/+3
|
* README.cygwin: Fix broken linkKarl Williamson2011-05-181-2/+2
|
* Internals.pod: Fix broken linksKarl Williamson2011-05-181-2/+2
|
* README.os2: Fix broken linksKarl Williamson2011-05-181-8/+8
|
* perlglossary: Fix broken linksKarl Williamson2011-05-181-2/+2
|
* cop.h: pod: Fix broken linksKarl Williamson2011-05-181-4/+4
|
* INSTALL: Change name so links to it aren't brokenKarl Williamson2011-05-181-1/+1
|
* POSIX.pod: fix broken linkKarl Williamson2011-05-181-1/+1
|
* Fix broken linkKarl Williamson2011-05-181-2/+3
|
* threads-shared: Fix broken linkKarl Williamson2011-05-181-2/+2
|
* perlxstut: Correct NAMEKarl Williamson2011-05-181-1/+1
|
* base.pm: pod: Remove obsolete referencesKarl Williamson2011-05-181-3/+3
|
* INSTALL: broken linkKarl Williamson2011-05-181-1/+1
|
* Assertion fails in multi-char regex matchKarl Williamson2011-05-182-4/+10
| | | | | | | | | | In '"s\N{U+DF}" =~ /\x{00DF}/i, the LHS folds to 'sss', the RHS to 'ss'. The bug occurs when the RHS tries to match the first two es's, but that splits the LHS \xDF character, which Perl doesn't know how to handle, and the assertion got triggered. (This is similar to [perl #72998].) The solution adopted here is to disallow a partial character match, as #72998 did as well.
* release_managers_guide: feedback from 5.15.0 bumpDavid Mitchell2011-05-181-24/+57
| | | | | | | | | | | The version bump from 5.14.0 to 5.15.0 didn't go at all smoothly. Update release_managers_guide based on that experience. Basically there were a couple of catch-22 situations with auto-generated files; namely uconfig.h and the pod/perl5150delta.pod link. Also, I've split the 'bump bleed to 5.15' and 'make maint-5.14 branch' instructions into two separate sections.
* buildtoc - fix a bug and add some commentsDavid Mitchell2011-05-181-2/+7
| | | | | | | while(readdir) doesn't auto-assign to $_ Also, make the informative output clear that its telling you like of files it will be processing, rather than that its actually processing it now.
* Bump the perl version in various places for 5.15.0David Mitchell2011-05-1827-187/+188
|
* update TOC for perl5150deltaDavid Mitchell2011-05-188-40/+51
|
* create perldelta for 5.15.0David Mitchell2011-05-183-4357/+4726
|
* Amend the readline()+signals caveatJosh ben Jore2011-05-141-2/+2
|
* Remove RC3 marker.v5.14.0Jesse Vincent2011-05-141-1/+0
|
* Make ‘require func()’ work with .pm abs pathv5.14.0-RC3Father Chrysostomos2011-05-112-2/+17
| | | | | | | | | | | | | | | | | | | | | | | | | As of commit 282b29ee485, pp_requires passes an SV to S_doopen_pm, instead of char*/length pair. That commit also used sv_mortalcopy() to copy the sv when trying out a .pmc extension: + SV *const pmcsv = sv_mortalcopy(name); When the path is absolute, the sv passed to S_doopen_pm is the very sv that was passed to require. If it was returned from a (non-lvalue) sub-routine, it will be marked TEMP, so the buffer gets stolen. After the .pmc file is discovered to be nonexistent, S_doopen_pm then uses its original sv to open the .pm file. But the buffer has been stolen, so it’s trying to open undef, which fais. In the mean time, pp_require still has a pointer to the stolen buffer, which now has a .pmc extenion, it blithely reports that the .pmc file cannot be found, not realising that its string has changed out from under it. (Actually, if the file name were just the right length, it could be reallocated and we could end up with a crash.) This patch copies the sv more kindly.
* RC3 bumpJesse Vincent2011-05-114-5/+7
|
* Remove the "RC2" marker in preparation for Wednesday's final release.Jesse Vincent2011-05-091-1/+0
|
* "fix bug; also prefix ?? matches with m due to 5.14 deprecation"Tom Christiansen2011-05-081-6/+6
| | | | | | | | | | | | | | | | | | | | I also fixed a bug in the original. I'm always getting C<eof> vs C<eof()> swapped in my brain, which is what had happened here. The old code didn't do what it said it did because it contrary to the comments didn't reset at each eof -- because it used the C<eof()> form which is all of ARGV rather than bare C<eof> for the last file read, and thus each per-file component of ARGV. I am concerned about the two paragraphs previous to that, because they use eof() and I am not perfectly clear that they should. But I left them as is. Jesse asked for "a lot of eyes", so if folks could please look at this patch and see whether it looks ok, I'd appreciate it. I did test it under blead, both with and without the prefixed m on the m?? matches, which is how I discovered it was buggy with the C<eof()> not C<eof>. --tom
* Updates to perlfunc to explicitly mention some of 5.14's new featuresv5.14.0-RC2Tom Christiansen2011-05-041-37/+50
| | | | somewhere other than perldelta.
* It's not 2012. - spotted by jdbJesse Vincent2011-05-031-1/+1
|
* typo fix spotted by tchristJesse Vincent2011-05-031-1/+1
|
* Bump Module::CoreList because the content changed since RC1 and we haveJesse Vincent2011-05-032-3/+3
| | | | nice, zealous porting tests
* RC1 -> RC2; push off the date of 5.14.0 until a week from tomorrowJesse Vincent2011-05-033-3/+4
|
* Documentation for sprintf updates in Perl 5.14Jesse Vincent2011-05-031-7/+22
|
* Doc changes for [perl #89750]Karl Williamson2011-05-033-4/+59
|
* regcomp.c: White space onlyKarl Williamson2011-05-031-4/+4
| | | | | A previous commit added an 'if' around this code. This now indents the block properly.
* PATCH: [perl #89750]: Unicode regex negated case-insensitivityKarl Williamson2011-05-033-1/+28
| | | | | | | | | | | | | This patch causes inverted [bracketed] character classes to not handle multi-character folds. The reason is that these can lead to very counter-intuitive results (see bug discussion). In an inverted character class, only single-char folds are now generated. However the fold for \xDF=>ss is hard-coded in, and it was too much trouble sending flags to the sub-sub routine that does this, so another check is done at the point of storing the list of multi-char folds. Since \xDF doesn't have a single char fold, this works.
* utf8.c: Add _flags version of to_utf8_fold()Karl Williamson2011-05-036-21/+39
| | | | | | | | | | And also to_uni_fold(). The flag allows retrieving either simple or full folds. The interface is subject to change, so these are marked experimental and their names begin with underscore. The old versions are turned into macros calling the new versions with the correct extra parameter.
* embed.fnc: Allow NULL arg to to_utf8_case()Karl Williamson2011-05-032-4/+3
| | | | | | | Code within the function doesn't assume that the parameter is non-null, and in fact the specials are retrieved by swash_init(). Having the parameter null just means that no specials will be retrieved in the current call.
* Small typo fixes in perldeltaJesse Vincent2011-05-031-4/+1
|
* Minor perldelta fixesFather Chrysostomos2011-05-031-10/+12
| | | | | | | | | | | • Remove C<...> around get-magic and set-magic. Those are prose descriptions of what is known internally as mg_get, SvGETMAGIC, SVs_GMG, etc. • Re-instate the message that 804b5feed removed, but in the form in which it appears in perldiag. • Remove the thing about version class methods. It’s a bug fix, not a problem (whether known or unknown :-), and not a significant one. • Spelling mistake
* skip t/io/eintr.t on production releasesDavid Mitchell2011-05-031-1/+6
| | | | | | | We already skip this test file on many platforms which don't have interruptible IO system calls. Extend this to unconditionally skip if it's an even (production) release version, so that we don't get false positives for other platforms we didn't know about.
* skip a problematic test on openbsd/threadTony Cook2011-04-271-0/+2
| | | | | I'd make this a TODO, but the test currently results in the watchdog firing, so harness/TEST would never see the "TODO".
* typoRobin Barker2011-04-271-1/+1
|