summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* bump version to 5.12.3-RC2v5.12.3-RC2Ricardo Signes2011-01-142-1/+2
|
* tweak perldelta for fixes in previous commitsRicardo Signes2011-01-141-1/+2
|
* [perl #76540] "print CONSTANT," gives double-freeDavid Mitchell2011-01-142-2/+23
| | | | | | | | | gv_init() has name and len args, but newCONSTSUB() (which it calls) doesn't have a len arg, so any trailing garbage in name gets used by newCONSTSUB. In the test case, this means that we end up attaching the const CV to both the "FOO" and qq{FOO, "\\n";\n} GVs. So it gets freed twice.
* tidy some code in gv_init()David Mitchell2011-01-141-6/+8
| | | | Use an intermediate variable cv to avoid lots of GvCV(gv)'s
* tiny prose fix to perldelta intro (thanks Zefram)Ricardo Signes2011-01-101-1/+1
|
* bump version to 5.12.3-RC1v5.12.3-RC1Ricardo Signes2011-01-092-0/+2
|
* update to Module::CoreList as of b43a7fcRicardo Signes2011-01-092-148/+2749
| | | | (could not be simply cherry-picked)
* update CoreList for 5.12.3Ricardo Signes2011-01-091-88/+705
|
* update perldelta diff statsRicardo Signes2011-01-081-4/+7
|
* bump version to 5.12.3 in anticipation of releaseRicardo Signes2011-01-0821-138/+138
|
* Socket.pm changed; bump versionRicardo Signes2011-01-081-1/+1
|
* B::Deparse changed; bump versionRicardo Signes2011-01-081-1/+1
|
* perldelta for cherry-picks since last updateRicardo Signes2011-01-081-0/+13
|
* [perl #73630] Build separate DTrace for miniperlDavid Leadbeater2011-01-041-3/+10
| | | | | | | | | | | | | As outlined in the RT ticket due to miniperl's dependencies differing to the final perl binary dtrace -G needs to be called separately for each. Build tested on Mac OS X 10.6, Solaris 11 and Scientific Linux with SystemTap from git. (Solaris is the only system I have access to where DTRACE_O actually gets defined. Neither the dtrace binary on OS X nor SystemTap's dtrace compatibility layer accept the -G option.) (cherry picked from commit 3d450a5dd4e8f9a7b2aba0b018f9fe078fb6aa30)
* Fix list of constants to import to make this test passRafael Garcia-Suarez2011-01-041-1/+1
| | | | (cherry picked from commit d9bf0e0a91525fcdd8099d78b891aa20066e9d1c)
* fix internal link in perlrepositoryRicardo Signes2011-01-031-1/+1
|
* perlreref.pod: NitsKarl Williamson2011-01-031-4/+5
| | | | Signed-off-by: David Golden <dagolden@cpan.org>
* Nit in perlrebackslash.podKarl Williamson2011-01-031-1/+1
|
* perlre: Add heading to separate unrelated paragraphsKarl Williamson2011-01-031-0/+2
| | | | | | I don't know where the text for the stuff below this new heading should go, but it clearly doesn't belon with what came before, so add a heading to separate them, perhaps rearranging things later
* Nits in perlre.podKarl Williamson2011-01-031-2/+3
|
* Update: re pragma is lexically scoped since Perl 5.9.5.Nick Johnston2011-01-031-1/+2
|
* Deparse correctly "no VERSION" [perl #75482]Rafael Garcia-Suarez2011-01-031-2/+2
|
* remove trailing spaces in perlvar.podDavid Golden2011-01-031-18/+18
|
* perlhack: fix formatting issuesKarl Williamson2011-01-031-19/+24
| | | | Change some lines so won't overflow 80 column width; make a link.
* perlreref: missing info, 80 col displayKarl Williamson2011-01-031-41/+64
| | | | | | The \p{Posix...} classes had not gotten added yet to the ref pod; there were some reformattings to make things display properly in an 80 column window.
* perlrecharclass: Clarify \p{Punct}, fix for 80 colKarl Williamson2011-01-031-9/+13
| | | | | While not strictly wrong, the hre was missing info for what \p{Punct} does.
* Fix Module::Build::Platform::cygwin runtime errorDavid Golden2011-01-031-5/+5
| | | | | | | | | | | This addresses runtime errors in Module::Build::Platform::cygwin as reported by Jesse Vincent. The changes are backported from the Module::Build repository and the version number has been slightly incremented to indicate a change from the version on CPAN. This hopefully addresses test errors in t/actions/installdeps.t, but the error seems specific to building perl on cygwin and has not been reported when Module::Build was tested on cygwin by CPAN Testers.
* perlebcdic.pod nits plus improve controls docsKarl Williamson2011-01-031-336/+329
| | | | | | The controls all now have names, and the part about \c\ has been corrected. The table widths have been changed; all recipes have been tested on the new tables.
* Edits to perlrecharclass.podKarl Williamson2011-01-031-98/+143
| | | | | | A number of clarification and wording edits have been made, fixing some broken links, and details especially on \d in the Unicode range. Fixed an incorrect character ordinal
* Nits in perlre.pod, x-referencing, broken linksKarl Williamson2011-01-031-89/+74
|
* Nits in perlunicode.podKarl Williamson2011-01-031-27/+35
|
* Clarify \c usage in perlrebackslash.podKarl Williamson2011-01-031-9/+17
|
* Nits in perluniintro.podKarl Williamson2011-01-031-16/+17
| | | | | Make accurate the advice about eighth-bit set characters, and a few editing improvements.
* Mention L<perlpolicy> and link to it in SEE ALSOÆvar Arnfjörð Bjarmason2011-01-031-1/+2
|
* Only all-upper case "special" POD sectionsÆvar Arnfjörð Bjarmason2011-01-031-16/+16
| | | | | | | "GETTING ACCESS TO THE REPOSITORY" is a bit too loud compared to "Getting access to the repository". The POD standard itself doesn't have anything to say about this, but most of our long =head1 sections in pod/*.pod don't use all-caps.
* Commit messages should start with a ~50 char summaryÆvar Arnfjörð Bjarmason2011-01-031-2/+10
| | | | | | | The first sentence is stolen from Git's own Documentation/SubmittingPatches. We have a lot of commit messages that overflow `git log --pretty=oneline', but it wouldn't hurt if we change that sooner rather than later.
* Nits in perlrebackslashKarl Williamson2011-01-031-8/+8
| | | | Signed-off-by: David Golden <dagolden@cpan.org>
* [perl #75656] lvalue subs don't copy on writeFather Chrysostomos2011-01-032-2/+10
| | | | | | | | | | | | The attached patch teaches pp_leavesublv about kine. For the record, a binary search points its digit at: From: Nicholas Clark <nick@ccl4.org> Date: Mon, 6 Jun 2005 09:08:45 +0000 (+0000) Subject: Shared hash key scalars can be safely copied as shared hash key scalars Shared hash key scalars can be safely copied as shared hash key scalars all the time.
* Fix typo in perlpolicy.podSteffen Mueller2011-01-031-1/+1
|
* Added our support policy to perlpolicy.pod.Jesse Vincent2011-01-031-0/+64
|
* [perl #78306] Clearify inc_version_list config in INSTALLZsbán Ambrus2011-01-031-0/+7
|
* Add info regarding AIX 7.1Rainer Tammer2011-01-031-32/+34
|
* bring perl5123delta up to date; cut unneeded bitsRicardo Signes2011-01-031-192/+22
|
* Fix some =/== nits in vms/vms.cCraig A. Berry2011-01-011-5/+4
|
* RT 78836: vms/vms.c: dubious expressionsNicolas Kaiser2011-01-011-2/+2
| | | | | | I noticed two dubious expressions that look as if they were intended to be assignments. The comment above the code says it's broken.
* Make perlio line buffer VMS record-oriented files on output.Craig A. Berry2011-01-012-1/+47
| | | | | | | | | | | | | | | | | | | | | When perlio flushes down to the unix layer, it can introduce a spurious record boundary when writing to a record-oriented file. Perl may create such files when doing edit-in-place or any other context where the file format is inherited from a previous version of the file. The problem can be eliminated by enabling line buffering on such files when they are opened. This was a regression in 5.10.0 since before that stdio's buffering performed the same function. N.B. Lines longer than the size of the perlio buffer will still result in multiple records -- a larger buffer may be necessary. For more details and discussion see: http://www.nntp.perl.org/group/perl.vmsperl/2010/11/msg15419.html Thanks to Martin Zinser for the problem report.
* Make PerlIOUnix_open honor default permissions on VMS.Craig A. Berry2011-01-011-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When perlio became the default and unixio became the default bottom layer, the most common path for creating files from Perl became PerlIOUnix_open, which has always explicitly used 0666 as the permission mask. This has the following undesireable effects on VMS: 1.) The execute bit is lost regardless of whether it's in the default permissions. 2.) Delete permission (which doesn't exist in the Unix permission mask) is copied from write permission, so granting write permission also grants delete even if it's not in the default permission mask. This can result in an inadvertent widening of permissions. 3.) System permissions (which don't exist in the Unix permission mask) are copied from owner permissions, so any distinction between system and owner is lost. 4.) ACLs are not inherited. For example, setting a default_protection ACE on a directory such that all world access is disallowed will be ignored; world will have the intersection of RWD (the final 6 in 0666) and whatever the default permissions are regardless of what the ACL says. Thus not inheriting ACLs can result in the inadvertent widening of permissions. The way to avoid all of this is to pass 0777 as the permissions to open(). In the VMS CRTL, 0777 has a special meaning over and above intersecting with the current umask; specifically, it allows Unix syscalls to preserve native default permissions. Details currently documented at: http://h71000.www7.hp.com/doc/732final/5763/5763pro_060.html#umask_routine
* Only use home-rolled prototypes on VMS when really necessary.Craig A. Berry2010-12-311-87/+2
| | | | | | | | | | | | | | | | | | | | The prototypes removed here, while in some ways superior to those provided in the system-supplied headers, in other ways conflict with them. The conflicts were masked in the default build by the fact that the macros mapping lower case names to upper case were undefined, so at compile time there were really two different prototypes even though at link time the symbols were the same. But the conflict broke the build when compiling with /NAMES=AS_IS to preserve symbol name case. Overall, whatever modest benefit maintaining our own prototypes might provide, it's just not worth the risk of conflict. A better approach would be to define __NEW_STARLET and work through whatever the compiler complains about. For sys$sigprc and lib$initialize, we do continue to provide our own prototypes (and add lower case to upper case mapping macros) because there are no system-supplied prototypes for them.
* Patch for Stratus VOS for extended file namesPaul Green2010-12-203-42/+73
| | | | | | | | | | | | The attached 1-line patch to hints/vos.sh defines a C macro that enables support for file names longer than 32 characters on the Stratus OpenVOS port of perl. As there are now some files in the base package whose names exceed 32 chars, this is an important change. This change only applies to OpenVOS (horay for the hints files)! I tested this change on OpenVOS Release 17.0.2ab. I have also updated the .pod files that refer to VOS/OpenVOS.
* Fix perl build problems on Stratus VOSPaul Green2010-12-022-13/+39
| | | | | | | This patch is a port of commit a5addb167c102dc5dcd1ab886caf0cb4f554eb05 to the 5.12 maintenance branch. It removes the extra "miniperl" dependency of the "all" target in Makefile.SH, and also tweaks ext/Socket/Socket.xs to build on systems that do not have the relevant IPv6 defines.
View Lorry Controller Status