summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* XS::Typemap: Tests for T_PACKEDSteffen Mueller2012-02-013-4/+91
|
* Document T_PACKEDARRAYSteffen Mueller2012-02-011-1/+15
|
* XS::Typemap: Document T_PACKEDSteffen Mueller2012-02-011-1/+32
|
* XS-Typemap: Document sharing mechanism for typemapsSteffen Mueller2012-02-011-0/+29
| | | | Thankfully, it's a one-liner now.
* Inline the XS-Typemap typemap fileSteffen Mueller2012-02-013-27/+31
|
* Document the exact format of a typemapSteffen Mueller2012-02-011-1/+68
| | | | | Including both the format of the content of a typemap file as well as the embedded typemap syntax.
* Typemaps: Start writing some general documentationSteffen Mueller2012-02-011-1/+45
|
* First stab T_REFREF docsSteffen Mueller2012-02-011-1/+8
| | | | | | | I am rather confident that this was added for some notion of symmetry and completion. It's only half-implemented and there are no known users in core or on CPAN. Candidate for deprecation (instead or in addition to documentation?)?
* Typemap tests: T_SHORT, T_U_INT, T_INT, T_LONGSteffen Mueller2012-02-013-14/+74
|
* Cleanup: Condense tests and add a fewSteffen Mueller2012-02-011-80/+34
|
* Minor documentation fixes and annotationsSteffen Mueller2012-02-012-5/+8
|
* Stop SvPVutf8 from forcing the POK flagFather Chrysostomos2012-01-312-2/+6
| | | | | | It was setting this even on magical variables, causing stringification not to bother calling FETCH, because the POK flag means ‘yes, I’m a bonified [sic] string, with nothing funny going on’.
* XS::APItest: svpv_magic.t: Correct test nameFather Chrysostomos2012-01-311-1/+1
|
* Make SvPVbyte return bytes for non-PVsFather Chrysostomos2012-01-314-5/+16
| | | | | Instead of just doing SvPV on something that is not a PV, SvPVbyte should actually do what it is advertised as doing.
* perldelta for ‘no overloading’ and qr//Father Chrysostomos2012-01-311-1/+7
|
* perldelta for stacked filetests and FETCHFather Chrysostomos2012-01-311-1/+5
|
* perldelta for stacked -tFather Chrysostomos2012-01-311-1/+5
|
* Test that SvPVutf8 works with magic varsFather Chrysostomos2012-01-312-2/+20
| | | | It didn’t until the previous commit.
* [perl #108994] Stop SvPVutf8 from coercing SVsFather Chrysostomos2012-01-316-3/+39
| | | | | | | | | | In shouldn’t destroy globs or references passed to it, or try to coerce them if they are read-only or incoercible. I added tests for SvPVbyte at the same time, even though it was not exhibiting the same problems, as sv_utf8_downgrade doesn’t try to coerce anything. (SvPVbyte has its own set of bugs, which I hope to fix in fifthcoming commits.)
* perldelta for read-only core globsFather Chrysostomos2012-01-311-0/+5
|
* XS::APItest: Move $VERSION further upFather Chrysostomos2012-01-311-2/+2
| | | | so it can be changed without one having to search for it.
* Increase $XS::APItest::VERSION to 0.35Father Chrysostomos2012-01-311-1/+1
|
* perldelta for B::COP::stashflagsFather Chrysostomos2012-01-311-1/+8
|
* B.pm: Document stashflagsFather Chrysostomos2012-01-311-0/+2
| | | | | (actually just list in; you have to know the internals to use these things anyway)
* perldelta up to 675dc5e1aFather Chrysostomos2012-01-311-1/+31
|
* Increase $File::Copy::VERSION to 2.23Father Chrysostomos2012-01-311-1/+1
| | | | | not 2.22, as that was used by 5.13.10, but the only changes in 5.13.10 were reverted for 5.13.11+.
* [perl #109104] File::Copy: Turn off ‘newline’ warningsFather Chrysostomos2012-01-311-1/+1
| | | | | | | | | These warnings exist to catch file operations on unchomped file names. But File::Copy should not be triggering them, otherwise it produces warnings for every copy("foo/bar\n", "baz/bar\n"), with no (easy) way to suppress the warning, as warnings are lexical. I don’t know how to test this portably.
* Remove use of study from splainFather Chrysostomos2012-01-311-1/+0
| | | | | It only helps with very long strings. It actually slows things down slightly when used on short strings.
* Increase $File::Glob::VERSION to 1.17Father Chrysostomos2012-01-311-1/+1
| | | | following commit ffa23acf6.
* Add blank lines around Configure's duplicate extension diagnostic.Nicholas Clark2012-01-311-1/+3
| | | | | | | The diagnostic message containing the duplicate extension did not stand out, particularly given that the immediately previous output is a very long line of found extensions. So add blank lines on either to make it easier to spot.
* Pod-Perldoc is now maintained on CPANFlorian Ragwitz2012-01-3125-167/+158
|
* Remove from perlfunc.pod the summaries of what's new/obsoleted in Perl 5.Nicholas Clark2012-01-311-16/+0
| | | | | Perl 5.000 isn't *new*. These days, people migrating to current Perl 5 aren't coming from Perl 4, so this section is redundant.
* Purge references to --libpod, an abbreviation for --libpodsNicholas Clark2012-01-312-2/+2
| | | | | | | | --libpods was removed from Pod::HTML in commit 3b49d8d9ac841d8e, and references to it removed in commit 6c6fc3be9a6e74e4. However, that commit missed the fact that 2 callers were not using the full name for the option, which works because Getopt::Long defaults to accepting unambiguous abbreviations.
* Configure now aborts with a diagnostic if it detects a duplicate extension.Nicholas Clark2012-01-311-0/+17
| | | | | | | | | | | | | | | | | | During the development process, if an extension module changes dual-life status it can move between ext/, dist/ and cpan/. If one uses git pull in a built tree across such a change, one can end up with the build tree in a messy state from which the 'distclean' target can't recover. Configure will spot both the old and new directories, and may wrongly categorise the extension as non-XS, resulting in obscure build failures after miniperl is build. In the general case, the "old" directory might contain files the user wants to keep, so it's not safe to automatically delete it. The only safe option is to ask the user to resolve the problem, hence with this change, if Configure detects such a situation it aborts with a diagnostic suggesting what to do. This isn't a problem that affects released tarballs.
* In B.xs, use *pvf() functions to reduce the number of API calls.Nicholas Clark2012-01-311-7/+5
| | | | This gives a small reduction in both source lines and object code size.
* diagnostics doesn't need to search for perldelta.pod in pre-5.005 locations.Nicholas Clark2012-01-312-7/+9
| | | | | | | | | | | | | | | | | | | Pods are installed into privlib. Before Perl 5.005, privlib didn't contain the version number in it, so 5.004 and 5.003 (etc) both installed to the same directory. perldiag.pod differed in not-quite compatible ways, so hacks were put in to (a) also install it in privlib with the version number in the filename (b) to hard link it to archlib, which always did contain the version number. 5.005 changed privlib to contain the version number, solving the underlying problem (strictly commit bfb7748a896459cc, described here: http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/1998-07/msg00136.html ) Commit a841533b5cf319b3 (Oct 2009) removed the first installation hack, Commit e8ea61279d90dbe9 (Jul 1998) removed the second. Hence the code to search in the "hacked" locations is no longer needed, and in the interests of clarity, should go.
* podcheck.t: Add commentKarl Williamson2012-01-301-0/+1
|
* locale.t: Add tests for fc()Karl Williamson2012-01-301-2/+22
|
* locale.t: process in sorted orderKarl Williamson2012-01-301-2/+2
| | | | for easier debugging, when debugging
* locale.t: White space onlyKarl Williamson2012-01-301-63/+67
| | | | | | | This indents code to account for a newly formed block around it, reflowing things to fit into an 80 column window. And it adjusts the indentation of a few other lines.
* locale.t: Add tests for IN_UNI_8_BITKarl Williamson2012-01-301-3/+12
| | | | These are more tests for commit b36bf33f6564c3e9a9ff131f4f3c9980b7a8af15
* locale.t: white space onlyKarl Williamson2012-01-301-11/+11
| | | | Properly indent this statement
* use locale; fc(""); shouldn't taint.Brian Fraser2012-01-301-1/+1
| | | | | fc() brought to life its own version of #39028. fc(""), like lc("") and friends, shouldn't taint the result.
* Increase the fallback value of MAXPATHLENDominic Hargreaves2012-01-301-1/+1
| | | | | | On systems without MAXPATHLEN or PATH_MAX defined (GNU/Hurd is an example of such a system), set MAXPATHLEN to 4096 rather than 1024; this increase creates parity with Linux.
* 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
|
View Lorry Controller Status