summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Moving :mmap out of core binary into a moduleLeon Timmermans2012-01-308-327/+373
|
* stat.t: Use $>, not just $< for skippingFather Chrysostomos2012-01-301-1/+1
| | | | This is the paranoid version of just using $>.
* [perl #108780] Make /foo$qr/ work under ‘no overloading’Father Chrysostomos2012-01-302-1/+18
| | | | | | | This changes the code in pp_regcomp to use the underlying REGEXP instead of the reference to it, when concatenating pieces to mark a larger regular expression. This makes /foo$qr/ work even under ‘no overloading’. It stopped working with commit a75c6ed6b.
* Update IPC-Cmd to CPAN version 0.76Chris 'BinGOs' Williams2012-01-303-15/+38
| | | | | | | | | | | | | | | | [DELTA] Changes for 0.76 Mon Jan 30 11:30:53 GMT 2012 ================================================= * Make the empty arg stripping the default again, with option to override this behaviour. Changes for 0.74 Mon Jan 30 10:24:30 GMT 2012 ================================================= * Applied patch from WATANABE Hiroaki [RT #74470] "Empty string cannot be passed to command" * Resolved [RT #74373] reported by Randy Stauner "Compilation error when POSIX.pm fails to load"
* Update MANIFESTFather Chrysostomos2012-01-291-0/+3
|
* Increase $Term::ReadLine::VERSION to 1.08Father Chrysostomos2012-01-291-1/+1
|
* Add Darin McBride to AUTHORSFather Chrysostomos2012-01-291-0/+1
|
* [perl #108470] Make Term::ReadLine use AE if availableDarin McBride2012-01-294-27/+172
| | | | | | | | | | | | Term::ReadLine only allows the Tk event loop to be called during a readline call. This should be updated to use AnyEvent which will still work with Tk, as well as any other event loop the user may need. With this patch, T::RL now uses AnyEvent if it is loaded, falling back to Tk otherwise; so the Tk mode won't be affected. T::RL::Stub has its own get_line. This does not honour the tkRunning flag at all. If I remove it, it's fine. This patch does so.
* Update IO-Compress to CPAN version 2.048Chris 'BinGOs' Williams2012-01-2934-145/+177
| | | | | | | | | | | [DELTA] 2.048 29 January 2012 * Set minimum zlib version to 1.2.0 * IO::Compress test suite fails with Compress::Raw::Zlib 2.047 and zlib < 1.2.4 [RT# 74503]
* Update Compress-Raw-Zlib to CPAN version 2.048Chris 'BinGOs' Williams2012-01-295-7/+11
| | | | | | | | [DELTA] 2.048 29 January 2012 * Set minimum zlib version to 1.2.0
* Update Compress-Raw-Bzip2 to CPAN version 2.048Chris 'BinGOs' Williams2012-01-296-7/+11
| | | | | | | | [DELTA] 2.048 29 January 2012 * No Changes
* lc.t: Add tests for previously broken IN_UNI_8_BITKarl Williamson2012-01-291-1/+10
| | | | This adds tests for commit b36bf33f6564c3e9a9ff131f4f3c9980b7a8af15
* pp.c: Can grow scalar by lessKarl Williamson2012-01-291-1/+3
| | | | | The max expansion when a Latin1 character is folded and converted to UTF-8 is '2' bytes per input byte, not the more general case.
* pod updates for fc and \FBrian Fraser2012-01-297-18/+94
|
* Implement the fc keyword and the \F string escape.Brian Fraser2012-01-2918-214/+815
| | | | | | | | | | | | | | | | | | | | | | Along with the simple_casefolding and full_casefolding features. fc() stands for foldcase, a sort of pseudo case (like lowercase), which is used to implement Unicode casefolding. It maps a string to a form where all case differences are erased, so it's a locale-independent way of checking if two strings are the same, regardless of case. This functionality was, and still is, available through the regular expression engine -- /i matches would use casefolding internally. The fc keyword merely exposes this for easier access. Previously, one could attempt to case-insensitively test two strings for equality by doing lc($a) eq lc($b) But that might get you wrong results, for example in the case of \x{DF}, LATIN SMALL LETTER SHARP S.
* Add the fc keyword in regen/feature.plBrian Fraser2012-01-294-6/+34
| | | | It doesn't do anything yet.
* utf8.h: Restore macro defn incorrectly trashed earlierKarl Williamson2012-01-291-1/+3
| | | | | | Commit 66cbab2c91fca8c9abc65a7231a053898208efe3 changed the definition of IN_UNI_8_BIT, but in so doing, lost the 2nd line of the macro; and I did not catch it. Tests will be added shortly.
* Add Windows 2008 to the list of Windows versions in perlportChris 'BinGOs' Williams2012-01-291-0/+2
|
* feature.h: Mask hints in CURRENT_FEATURE_BUNDLEFather Chrysostomos2012-01-282-2/+4
| | | | | | | | | | | | Otherwise CURRENT_FEATURE_BUNDLE will end up including any hints added later that happen to use higher bits. This was causing autobox to turn off all features, causing failures for Dist::Zilla::PluginBundle::AVAR. I’m not adding tests for this, as such tests would need constant tweaking in future perl developement. What autobox is doing is naughty and unsupported anyway.
* [perl #109264] ->method(my(...)) forcing lvalue cxFather Chrysostomos2012-01-282-1/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A simple my($foo,$bar) list is flagged as an lvalue: $ ./perl -Ilib -MO=Concise -e 'my($foo,$bar)' 7 <@> leave[1 ref] vKP/REFC ->(end) 1 <0> enter ->2 2 <;> nextstate(main 1 -e:1) v:{ ->3 6 <@> list vKPM/128 ->7 3 <0> pushmark vM/128 ->4 4 <0> padsv[$foo:1,2] vM/LVINTRO ->5 5 <0> padsv[$bar:1,2] vM/LVINTRO ->6 -e syntax OK That 128 that the list op is the same flag as LVINTRO. When a method call is compiled, the list op for the argument list is itself converted into an entersub op. That LVINTRO flag is never turned off. So foo->bar(my($foo,$bar)) becomes this: $ ./perl -Ilib -MO=Concise -e 'foo->bar(my($foo,$bar))' 9 <@> leave[1 ref] vKP/REFC ->(end) 1 <0> enter ->2 2 <;> nextstate(main 1 -e:1) v:{ ->3 8 <1> entersub[t4] vKMS/LVINTRO,TARG ->9 3 <0> pushmark sM/128 ->4 4 <$> const[PV "foo"] sM/BARE ->5 5 <0> padsv[$foo:1,2] lM/LVINTRO ->6 6 <0> padsv[$bar:1,2] lM/LVINTRO ->7 7 <$> method_named[PV "bar"] ->8 -e syntax OK This was rarely a problem until commit da1dff948 added lvalue check- ing for method calls (a fifth bug fix in that commit not mentioned in the commit message). Calling the method will now result in ‘Can't modify non-lvalue subrou- tine call’ unless the method has the :lvalue attribute. Before that, this would only cause problems with lvalue methods: $ perl -le ' sub clear_queue:lvalue { warn "called"; undef } 3==main->clear_queue(my ($id, $name)) ' called at -e line 2. Can't return undef from lvalue subroutine at -e line 3. Calling it with ($id, $name) was fine, and allowed undef to be returned. Perl_localize in op.c (which is called for my, our and local) calls my() (aka Perl_my_attrs) on the list itself for my or our. Perl_my_attrs was setting flags on the list, not just on its children. So this commit modifies my_attrs not to set any flags on the list op itself. local() was not affected, as it goes through op_lvalue_flags instead of my_attrs, and op_lvalue_flags doesn’t set flags on list ops (I mean ops of type OP_LIST, not listops in general). I added tests for it anyway.
* Update IO-Compress to CPAN version 2.047Chris 'BinGOs' Williams2012-01-2939-221/+410
| | | | | | | | | | | | | | [DELTA] 2.047 28 January 2012 * Set minimum Perl version to 5.6 * IO::Compress::Zip - In one-shot zip, set the Text Flag if "-T" thinks the file is a text file. - In one-shot mode, wrote mod time & access time in wrong order in the "UT" extended field.
* Update Compress-Raw-Zlib to CPAN version 2.047Chris 'BinGOs' Williams2012-01-298-23/+187
| | | | | | | | | | | | | | | | | [DELTA] 2.047 28 January 2012 * Allow flush to be called multiple times without any intermediate call to deflate and still return Z_OK. In the code below $status was Z_BUF_ERROR before this change. $def->flush(...); $status = $def->flush(...); * Added support for zlibCompileFlags * Set minimum Perl version to 5.6
* Update Compress-Raw-Bzip2 to CPAN version 2.047Chris 'BinGOs' Williams2012-01-287-10/+18
| | | | | | | | [DELTA] 2.047 28 January 2012 * Set minimum Perl version to 5.6
* Trim directory extension in pathify under EFS.Craig A. Berry2012-01-281-46/+36
| | | | | | | | | | | When Extened Filename Syntax (EFS) is in effect, 1fe570cc5e24ee changed the age-old behavior of trimming the directory extension off a directory filename when the path is in Unix syntax. EFS really has nothing to do with the necessity to trim .DIR;1 from the name, so remove the conditional check for EFS from the existing code. This gets three more tests passing under EFS in vms/ext/filespec.t.
* Fix bug #109206: ANCH_MBOL with while /.*/gYves Orton2012-01-292-3/+15
| | | | | | We had a fencepost error when ANCH_MBOL was enabled that meant we did not "see" matches at the end of string. This fixes the problem and adds tests.
* accidentally used my work email for a commit so add it to checkAuthors.plYves Orton2012-01-291-0/+1
|
* fix variable not shared warnings coming from the use statement being ↵Yves Orton2012-01-281-2/+4
| | | | executed too early
* Increase $subs::VERSION to 1.01Father Chrysostomos2012-01-281-1/+1
|
* checkAUTHORS.pl: Add another (old?) address for JuerdFather Chrysostomos2012-01-281-0/+1
|
* [perl #21396] documentation error in subs.pmJuerd Waalboer2012-01-281-1/+1
|
* Adjust skip counts in t/op/filetest_t.t.Craig A. Berry2012-01-281-3/+3
| | | | | Follow-up to 8db8f6b697e6f, where new tests were added without changing the (implicit) skip count of 1.
* Restore directory extension and version in fileify under EFS.Craig A. Berry2012-01-282-77/+9
| | | | | | | | | | | | | | | | | | | | | | In df2786654 and 8a5aa89570, the traditional behavior of adding the .DIR;1 onto a fileified directory spec was removed when operating under Extended Filename Syntax. Various scary comments were added about its being a bug to add a type and version onto a Unix-style path, but actually the CRTL appears to be perfectly happy with, for example: stat('/foo/bar/baz.dir;1'); and without the extension, the home-grown rmdir() fails in the case of a directory with no preceding path information. E.g., rmdir('foo'); was failing because there was no internal translation to foo.dir before passing it to SYS$ERASE. Moreover, even if there were something wrong with adding .DIR;1, it has nothing to do with EFS.
* filelify shouldn't always escape dots.Craig A. Berry2012-01-281-2/+2
| | | | | | | | | | | | | | | Follow-up to a9fac63d75d9222a73fbf511ca58ae1d66cbf9a7. It turns out that the CRTL doesn't handle the escapes when the path is in Unix syntax (even though it requires them in native syntax). stat('foo/bar.baz.dir;1') is ok, but stat('foo/bar^.baz.dir;1') fails. So skip the escaping if there is a slash anywhere in the path.
* ExtUtils::ParseXS: Changelog, version bump for dev releaseSteffen Mueller2012-01-286-5/+21
| | | | | Upgrade the version in ExtUtils::ParseXS to 3.13_01 for a development release.
* mymalloc isn't thread safe (rurban)H.Merijn Brand2012-01-271-1/+2
|
* Allow prototypes (_@) and (_%)Rafael Garcia-Suarez2012-01-274-6/+21
| | | | | | Those will be equivalent to (_;@) and (_;%) ; since perlsub already states that the semicolon is redundant before @ and % this is in line with the existing documentation.
* Show test names in outputRafael Garcia-Suarez2012-01-271-5/+5
|
* Make blead upstream for warnings.pmFather Chrysostomos2012-01-261-1/+1
| | | | | | This isn’t even a dual-life module. Why it has its own entry I don’t know; but in any case it has to have blead for upstream, otherwise cmp_version.t skips it.
* Increase $warnings::VERSION to 1.13Father Chrysostomos2012-01-262-2/+2
|
* Allow ${^WARNING_BITS} to turn off lexical warningsFather Chrysostomos2012-01-264-14/+28
| | | | | | | | | | | | | | Various magical modules copy hints from one scope to another. But copying ${^WARNING_BITS} doesn’t always copy the same hints. If lexi- cal warnings are not on at all, ${^WARNING_BITS} returns a different value depending on the current value of $^W. Setting ${^WARNING_BITS} to its own value when $^W is true will stop $^W from being able to control the warnings in the current compilation scope. Setting ${^WARNING_BITS} to its own value when $^W is false causes even default warnings to be suppressed. This commit makes undef a special value that represents the default state, in which $^W controls warnings.
* pat.t: Test that . overloading gets passed qr refFather Chrysostomos2012-01-261-1/+18
| | | | | | This is something that my sample patch in ticked #108780 (for fixing /foo$qr/ under ‘no overloading’) would have broken had it been applied.
* stat.t: Skip test when running as rootRainer Tammer2012-01-261-0/+1
|
* Bump $Unicode::UCD::VERSION after commit c3e5bc54acca7110.Nicholas Clark2012-01-252-1/+7
|
* Update list of files for a minimal installation in INSTALL.Andy Dougherty2012-01-251-91/+86
| | | | | | | Update the minimal list of files for 5.15.7, and also for Debian's perl-5.10.1 base package (which is what is in the Debian stable distribution at present). These lists do not include any explicit advice about what to name those stripped down installations.
* Correctly escape UTF-8 in hash keys in uninitialized warningsRafael Garcia-Suarez2012-01-252-3/+4
|
* Initialize buffer to an empty string to avoid spurious uninitialized warningsRafael Garcia-Suarez2012-01-251-1/+1
|
* Update known_pod_issues.dat for x2p/psedChris 'BinGOs' Williams2012-01-251-0/+1
|
* Fix pod error in Unicode::UCDChris 'BinGOs' Williams2012-01-251-0/+1
|
* Update DB_File to CPAN version 1.826Chris 'BinGOs' Williams2012-01-255-5/+10
| | | | | | | | | [DELTA] 1.826 25 Jan 2012 * t/db-btree.t - fix use of "length @array" [RT ##74336]
* Revert "Regen known_pod_issues.dat"Chris 'BinGOs' Williams2012-01-251-11/+0
| | | | | | This reverts commit 5fa409a90f64110c5708f7141b376e9bdc54fbe2. Resolved by update of Pod-Parser to version 1.51
View Lorry Controller Status