summaryrefslogtreecommitdiff
path: root/dist
Commit message (Collapse)AuthorAgeFilesLines
* Implement the fc keyword and the \F string escape.Brian Fraser2012-01-293-4/+11
| | | | | | | | | | | | | | | | | | | | | | 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.
* 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.
* Safe.pm: Make sure SWASHNEW is properly loadedKarl Williamson2012-01-202-5/+9
| | | | | | | | This module was depending on testing code points in the upper Latin1 range causing utf8_heavy.pl. However a recent performance improvement caused those code points to skip the loading. This just changes the code points to two higher values that cause it to load, and until and if it changes again, will fix things.
* Merge branch 'bingos/release-5.15.7' into bleadChris 'BinGOs' Williams2012-01-202-3/+698
|\
| * Update Module::CoreList for v5.15.7Chris 'BinGOs' Williams2012-01-202-3/+698
| |
* | Copyright update for ExtUtils::{ParseXS,Typemaps}Steffen Mueller2012-01-205-10/+6
| | | | | | | | Also removes a few lines of dead code
* | Fix parse problem with embedded typemapsSteffen Mueller2012-01-204-6/+5
|/ | | | | If an embedded typemap was found in certain locations, we got spurious parse failures. Mea culpa.
* Better typemap error reportingSteffen Mueller2012-01-203-7/+64
| | | | | If we couldn't find a typemap for a given C type, this now gives a list of available, mapped C types.
* EU::Typemaps: Make oneliner in docs more portableSteffen Mueller2012-01-201-1/+1
| | | | | Hopefully, anyway, by using double quotes (win32) and Perl's q quoting construct inside.
* Bump ExtUtils::ParseXS version for doc referencesSteffen Mueller2012-01-204-4/+4
|
* EU::Typemaps: Helper module for easy typemap inclusion in XSSteffen Mueller2012-01-194-0/+290
| | | | | | | | | In order to be able to deprecate certain typemaps from the core and send them to a peaceful retirement on the CPAN, it's necessary to make it easy to share and include these typemaps in case they're used despite CPAN greps claiming the opposite. This helper module facilitates non-copy-and-paste sharing of typemaps by adding a dependency and including a single line of code in the XS.
* EU::Typemaps: Implement embedded-typemap dumpingSteffen Mueller2012-01-193-2/+60
| | | | | This method will return a string representation of the typemap object that can be included *verbatim* in an XS file.
* Update Locale-Maketext to CPAN version 1.22Chris 'BinGOs' Williams2012-01-172-1/+14
| | | | | | | [DELTA] 2012-01-14 * Minor POD documentation update to sync with upstream blead.
* Increase $Math::BigInt::VERSION to 1.998Father Chrysostomos2012-01-161-1/+1
|
* BigInt.pm: Suppress overload warningFather Chrysostomos2012-01-161-0/+3
| | | | BigInt.pm intentionally registered an unregisterable op.
* Bump ExtUtils::Manifest version due to commits 97bae9c5 and bf081550Chris 'BinGOs' Williams2012-01-151-1/+1
|
* Bump autouse version due to commit f965e9d4aChris 'BinGOs' Williams2012-01-151-1/+1
|
* [perl #108224] B::Deparse doesn't recognize for continue blockHojung Youn2012-01-142-1/+45
| | | | | | | | | | | | | | | | B::Deparse foreach scoping problem was fixed at cf24a84005, which was issued at #30504. But B::Deparse was blinded temporarily by this commit so that it couldn't recognize foreach continue block for a moment. foreach statement generates 'nextstate', 'stub', 'leave', or 'scope' root opcode at will when foreach statement is not used as a oneline statement modifier. So all the case of opcodes should be checked. Some tests for foreach scoping and continue block are attached. related: #30504
* Stop inadvertently skipping Spec.t on VMS.Craig A. Berry2012-01-141-4/+4
| | | | | | | | | ae5a807c7dcf moved a check against $@ away from the eval it was checking and inserted another eval in between, the effect of which was to make the tests that can only run on VMS get skipped there too. Ouch. There are other problems with ae5a807c7dcf, but this is a start.
* Upgrade Pod-Perldoc to CPAN version 3.15_15Ricardo Signes2012-01-0624-903/+9804
|
* cflags does not exists in Config.pm; use ccflagsambs2012-01-0512-13/+13
| | | | | | [dagolden bumped $VERSION and added ambs to the AUTHORS file] Signed-off-by: David Golden <dagolden@cpan.org>
* Correct bug-report email in IO docsFather Chrysostomos2012-01-037-14/+15
| | | | This was mentioned in ticket #75156.
* Packlist.t: add bug numberFather Chrysostomos2012-01-031-1/+1
|
* ExtUtils::Packlist: Restore 5.005 compatibilityFather Chrysostomos2012-01-021-1/+1
| | | | I think. I haven’t actually tested it.
* [perl #107410] Tests for used-once warnings from ExtUtils::PacklistFather Chrysostomos2012-01-021-2/+14
|
* Removed 'once' warnings in ExtUtils::Packlist::mkfh.Joel Berger2012-01-021-0/+1
| | | | Fixes cpan bug #50315.
* Increase $ExtUtils::Packlist::VERSION to 1.46Father Chrysostomos2012-01-021-1/+1
|
* Current VMS can handle filenames with spaces.Craig A. Berry2011-12-311-0/+2
| | | | | | If they are escaped and on an ODS-5 volume, that is. We then have to clean up all versions of the files created by a test we weren't running before.
* Allow Data::Dumper to load on miniperlFather Chrysostomos2011-12-311-2/+3
| | | | | For a long time it has been doing eval { require XSLoader }, but XSLoader will load on miniperl, it’s just XSLoader::load() that fails.
* Increase $Data::Dumper::VERSION to 2.135_03Father Chrysostomos2011-12-311-2/+2
| | | | | I’m about to make a change, and 2.135_02 has already been used by a CPAN dev release.
* ExtUtils::ParseXS: Bump versions to 3.11Steffen Mueller2011-12-295-5/+8
| | | | | | | This is necessary for a CPAN release that fixes a versioning problem in version 3.09 (CPAN RT #73555). No functional changes.
* Escape double-quotes in generated #line directivesSteffen Mueller2011-12-284-7/+45
| | | | | | | | | | | | | | | #line directives can be generated from commands. Those may be using double quotes. That may not be considered friendly by preprocessors when the result looks anything like this #line 123 "perl -e "foo"" Input on whether the following is portable would be appreciated. #line 123 "perl -e \"foo\"" gcc is happy with it. I know. The world's not just win32, osx, and linux with a choice between three compilers.
* perlxstut: keep indentation consistent within exampleFather Chrysostomos2011-12-271-2/+2
|
* [perl #102622] perlxstut: Add SvGETMAGIC to exampleFather Chrysostomos2011-12-261-2/+5
|
* Skip failing DD tests under 5.6Father Chrysostomos2011-12-251-1/+7
|
* Fix DD’s vstring tests unter 5.6Father Chrysostomos2011-12-251-1/+6
|
* Make DD dump *{''} correctly under 5.6Father Chrysostomos2011-12-253-3/+18
| | | | | | 5.6 is strangely buggy, in that *{""} stringifies as "*main::\0". And then there are some other strange eval bugs that the tests have to work around.
* Make DD dump *{''} properlyFather Chrysostomos2011-12-253-4/+20
| | | | | | | | | This typeglob is an oddity, in that it stringifies as *main::, but cannot be reached under that name, because *main:: produces *main::main::. The former is $::{""}; the latter $::{"main::"}. I was inadvertently triggering this in 5.8 when I added a test a while back for typeglobs will nulls in their names.
* [perl #101162] DD support for vstringsFather Chrysostomos2011-12-253-8/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for vstrings to Data::Dumper, in both Perl and XS implementations. Since the actual vstring cannot be obtained from pure Perl, there is a new _vstring XS function that the PP implementation uses, falling back to sprintf "%vd" if XS is not available. The former dumps v1.2_3 cor- rectly, while the latter produces v1.23. (I could make it use B to extract the correct string, but XS is likely to be unavailable in those circumstances where B is also unavailable [i.e., miniperl], so it didn’t seem worth the effort.) Some Perl versions (read: *all* released versions as of this message) let vstring magic linger too long on strings that have been modified. So that is checked for, but the bug is probed at compile time and the code is #ifdeffed or use-constanted out when the bug is not present. Due to the definition of the _bad_vsmg constant, I had to move XSLoader::load into the BEGIN block. Since I was putting it there, I combined it, the $Useperl = 1 and the eval{} into one statement, for speed. Since I was putting XSLoader::load into a BEGIN block, $VERSION needed to be in one, too.
* Increase $Data::Dumper::VERSION to 2.135_02Father Chrysostomos2011-12-251-2/+2
|
* [perl #86060] $( $| $) need braces in regexpsFather Chrysostomos2011-12-242-1/+9
|
* deparse.t: Automatically count __DATA__ testsFather Chrysostomos2011-12-241-2/+3
| | | | | | | I didn’t know that done_testing could take an argument. This elimi- nates the manual fiddling of the test count every time a test is added to __DATA__. For other tests, which are the exception, we still have the safety of a test count to make sure the tests actually run.
* Deparse the /d flag with implicit featuresFather Chrysostomos2011-12-242-1/+18
| | | | | | | | | | | Before the recent feature revamp (2fc860ee1e0), loading the unicode_strings feature would always set the feature_unicode %^H ele- ment, even though the core did not actually use it. Now it is some- times not set. So we have to check the hint bits as well. Since feature.pm has it hardcoded, load feature.pm to get the right bit. The stuff with $feature_bundle_mask is redundant, but it avoids load- ing feature.pm unnecessarily.
* Deparse /$#a/ correctlyFather Chrysostomos2011-12-242-3/+7
| | | | | | | | | | | | | | | | | This is related to 4b58603b60. This time it’s this op tree that pure_string can’t handle: 8 </> match() vK/RTIME ->9 7 <|> regcomp(other->8) sK/1 ->8 3 <1> regcreset sK/1 ->4 6 <1> av2arylen sK/1 ->7 5 <1> rv2av[t2] sKR/1 ->6 4 <#> gv[*a] s ->5 In writing a test for this, I triggered a case that 415d4c68d missed (only $a and $b are exempt from strict vars, not @a and @b), so that is fixed in the same commit.
* Deparse.pm: Document that strict vars and subs workFather Chrysostomos2011-12-241-1/+1
|
* [perl #24027] Deparse strict vars and subsFather Chrysostomos2011-12-242-17/+51
| | | | | | | B::Deparse only supported strict refs till now, and not the other two. The hints were always present, but were being ignored. It was more complicated than simply printing out the pragma settings. Variables have to be qualified, too, under strict vars.
* Fix Deparse ambient_pragmas/strict regressionFather Chrysostomos2011-12-242-0/+20
| | | | | | | | | | | | | | | | | | | | | This commit fixes a regression introduced by b50b2058. ambient_pragmas makes changes to %^H, which affect the currently com- piling scope. BEGIN { new B'Deparse -> ambient_pragmas strict => 'all'; } use 5.012; # no strict here B::Deparse really does know too much about perl’s internals. It is calling strict.pm’s internal routines, which now set %^H, so Deparse has to localise it. Since it is very easy to write tests in evals that simply do not run (I actually did that when trying to test this, and was puzzled as to why everything was passing anyway), I have restored the test count. Sorry, Nicholas.
* Deparse.pm: Document that use feature is supportedFather Chrysostomos2011-12-241-1/+2
|
* Deparse all features with ‘use/no feature’Father Chrysostomos2011-12-242-18/+33
|
* Deparse implicit with ‘use feature’Father Chrysostomos2011-12-242-20/+80
| | | | | | | | | When a version declaration has been seen, it’s not possible to deparse the code perfectly correctly, but using ‘no feature; use feature "5.14"’ is a reasonable tradeoff. See also commit 1c74777c25. This necessitated sorting %^H keys that are output to keep tests pass- ing. Previously they were relying on phases of the moon.
View Lorry Controller Status