summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Assume we have sane C89 memcmp()Aaron Crane2017-10-2133-414/+32
| | | | | | | "Sane" means that it works correctly on bytes with their high bit set, as C89 also requires. We therefore no longer need to probe for and/or use BSD bcmp().
* Drop support for PowerUX / Power MAX OSAaron Crane2017-10-214-222/+2
| | | | | It is almost impossible to find any information about this platform on the internet, which strongly suggests that it's as dead as dead can be.
* Assume we have C89 memcpy() and memmove()Aaron Crane2017-10-2133-509/+5
| | | | We can therefore also avoid probing for and/or using BSD bcopy().
* Don't look for a "safe" memcpy()Aaron Crane2017-10-2128-178/+7
| | | | | | | | | | | | | C89 says that, if you want to copy overlapping memory blocks, you must use memmove(), and that attempt to copy overlapping memory blocks using memcpy() yields undefined behaviour. So we should never even attempt to probe for a system memcpy() implementation that just happens to handle overlapping memory blocks. In particular, the compiler might compile the probe program in such a way that Configure thinks overlapping memcpy() works even when it doesn't. This has the additional advantage of removing a Configure probe that needs to execute a target-platform program on the build host.
* Assume we have C89 memset()Aaron Crane2017-10-2133-257/+7
| | | | This means we also never need to consider using BSD bzero().
* Remove USE_STRUCT_COPY in favour of C89 struct assignmentAaron Crane2017-10-2124-112/+2
| | | | | At least for now, we retain the StructCopy() macro, but its definition always just uses struct assignment.
* Configure: fix nl_langinfo_l() probeAaron Crane2017-10-211-38/+41
| | | | This corresponds to metaconfig ad82f5bfbeafc125c0aed2b83391ed8d43bf31b2.
* Add Configure changes to perldeltaH.Merijn Brand2017-10-211-2/+28
|
* Add new Configure probesH.Merijn Brand2017-10-2115-28/+532
| | | | | | | This is a merge off several new probes in metaconfig done in the new shared developing environment by several authors Thanks to all that contributed!
* Today's M::CL is up on CPAN alreadySteve Hay2017-10-211-1/+1
|
* Prepare Module::CoreList for 5.27.6Steve Hay2017-10-214-3/+33
|
* Bump version to 5.27.6Steve Hay2017-10-2022-136/+136
|
* perldelta - Fix version for the next run of Porting/acknowledgements.plSteve Hay2017-10-202-2/+2
| | | | | And fix the template file so that the impending version bump will leave it correct for next time too.
* New perldelta for 5.27.6Steve Hay2017-10-2011-102/+550
|
* Tick off 5.27.5Steve Hay2017-10-201-1/+1
|
* Add epigraph for 5.27.5Steve Hay2017-10-201-0/+17
|
* Perl 5.27.5 todayv5.27.5Steve Hay2017-10-201-0/+1
|
* Finalize perldeltaSteve Hay2017-10-201-2/+26
|
* Update Module::CoreList for 5.27.5Steve Hay2017-10-201-4/+152
|
* perldelta - Fix broken linksSteve Hay2017-10-201-4/+5
|
* perldelta - Remove boilerplateSteve Hay2017-10-201-341/+0
|
* perldelta - Update selected bug fixes etcSteve Hay2017-10-201-8/+23
|
* perldelta - Update modulesSteve Hay2017-10-201-1/+93
|
* Suppress spurious corelist-perldelta.pl warningSteve Hay2017-10-201-1/+1
|
* Teach corelist-perldelta.pl about libnet, podlators and Sub::UtilSteve Hay2017-10-201-2/+21
|
* Porting/Maintainers.pl - version's vxs.inc is now CUSTOMIZED as wellSteve Hay2017-10-202-0/+2
|
* Porting/Maintainers.pl - NEXT is CUSTOMIZEDSteve Hay2017-10-202-0/+3
|
* Deparse.t tweakFather Chrysostomos2017-10-191-1/+1
| | | | | | | | The revert two commits ago causes B::Deparse to go through a different code path when dumping the constant. Ideally the output should be the same either way (i.e., consistently with or without a semicolon, not sometimes one way and sometimes the other). But for now, just make the test more lenient.
* perldelta for 14062320fFather Chrysostomos2017-10-191-0/+7
|
* Temporarily revert CV-in-stash optimisationFather Chrysostomos2017-10-192-1/+2
| | | | | This reverts two hunks from 6881372e19 to allow CPAN modules some time to conform to the optimisation.
* Update win32/config_H.[gv]c canned configuration filesSteve Hay2017-10-192-3165/+4134
| | | | | | | | | | This is done using the regen_config_h targets in the Windows makefiles, being careful to restore a couple of things otherwise lost from the config_H.gc file (a couple of STRINGIFY #undefs, comments above the HASATTRIBUTE_* #defines, and the #define of HAS_MKSTEMP). The files are now in sync with the top-level master configuration file, config_h.SH.
* Use SvLEN_set/SvCUR_set in a few extra locationsNicolas R2017-10-193-5/+5
| | | | | | SvLEN was set without using the generic macro SvLEN_set. Use it in three extra locations, and also use SvCUR_set instead of SvCUR.
* Merge branch 'smoke-me/ilmari/exec-empty-argv' into bleadDagfinn Ilmari Mannsåker2017-10-184-15/+37
|\
| * Perldelta for exec PROGRAM LIST with empty LISTDagfinn Ilmari Mannsåker2017-10-181-1/+5
| |
| * [perl #131730] Fix exec PROGRAM LIST with empty LIST on VMSDagfinn Ilmari Mannsåker2017-10-181-8/+8
| | | | | | | | | | Only when being Unixish, because I have no idea if setup_argstr()/vms_do_exec() handle it.
| * [perl #131730] Fix exec PROGRAM LIST with empty LISTDagfinn Ilmari Mannsåker2017-10-182-6/+24
|/ | | | | | | | | | | | | | | | | This should call execvp() with an empty argv array (containing only the terminating NULL pointer), but was instead just returning false (and not setting $!). Executing a program with an empty argv array is valid ISO C: it merely requires argc to be nonnegative and argv[argc] to be NULL. POSIX states that that argv[0] "should point to a filename string that is associated with the process being started", but "should" only applies to applications claiming strict POSIX conformance. Perl does not, and certainly should not impose it on perl programs. This also requires handling the case where both PROGRAM and LIST are empty, to avoid calling execvp(NULL, …), which _is_ invalid. I've made it return ENOENT, which it the error POSIX specifies for execvp("", …).
* Upgrade Test-Simple from version 1.302101 to 1.302103Steve Hay2017-10-1863-66/+128
|
* the unopened test should use a file handle distinct from "OTHER"Tony Cook2017-10-171-1/+2
| | | | used a name and added a comment so this isn't broken again
* [perl #127063] suppress warning on assigning 0 to $[Tony Cook2017-10-173-5/+9
|
* PERL5LIB documentation: '.' is no longer in @INC by defaultLukas Mai2017-10-161-4/+4
|
* customise Pod::Perldoc to fix output misbehaviourZefram2017-10-163-11/+7
| | | | | | | | | | | | | | | | | Pod::Perldoc has, since version 3.20, exhibited various kinds of misbehaviour relating to a bad default choice of formatter. Output has sometimes appeared mangled due to the newly-default formatter emitting unportable escape sequences, and sometimes there has been a more severe output failure due to perldoc making unportable changes to pager configuration in an attempt to make the escape sequences work. This is discussed in [perl #131762]. In the upstream instance of the module there have been tweaks to the unportable behaviour, but not an actual fix. In order to make the core distro ship a reliably-working version of perldoc, this patch customises Pod::Perldoc to implement the obvious fix for the portability problems. The fixed version defaults to the ToText formatter, which produces properly plain text that will go through any pager. It never attempts any change to pager configuration.
* [perl #124349] deprecation warning on hostname() with argumentsTony Cook2017-10-162-10/+27
|
* Use preprocessor check for some DEBUG_X_TESTNicolas R2017-10-162-7/+25
| | | | | | | | | Most of the DEBUG_?_TEST calls are already protected by one '#idef DEBUGGING' check, but noticed a few of them which were not protected in sv.c and toke.c We should avoid these extra 'if' statements if perl is not compiled with debug option: -DDEBUGGING.
* (perl #131982) update the set/getpriority documentation tooTony Cook2017-10-161-0/+6
|
* (perl #131982) provide constants for get/setpriority in POSIX.pmTony Cook2017-10-165-2/+29
| | | | | | <sys/time.h> isn't necessarily needed, but apparently increases portability, since the rusage structure defined in <sys/resource.h> has struct timeval members.
* Document that POSIX::abs, ::alarm, ::atan2, ::chdir, ::chmod need explicit ↵James E Keenan2017-10-152-15/+39
| | | | | | | | argument. Reformat code in one foreach block for readability. Make podcheck happy. For: RT #132145
* pp.c: delete dead cpp-conditional declarationAaron Crane2017-10-151-8/+0
| | | | | | | | This was added in commit dfe9444ca7881e716e9e8feaf20b55da491363ca (February 1998, for Perl 5.004_60) by Andy Dougherty, and its comment says that, even then, he thought it was unneeded. But the perl5 repo has ever defined the NEED_GETPID_PROTO cpp symbol that guards this declaration, so this ability has clearly never been used.
* Remove out-of-date mention of USA presidentSmylers2017-10-151-5/+6
| | | | | Avoid having to continue to update this every time the president changes by replacing Barack Obama with Ada Lovelace.
* RT#131000: splice doesn't honour read-only flagAaron Crane2017-10-154-2/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | The push and unshift builtins were correctly throwing a "Modification of a read-only value attempted" exception when modifying a read-only array, but splice was silently modifying the array. This commit adds tests that all three builtins throw such an exception. One discrepancy between the three remains: push has long silently accepted a push of no elements onto an array, whereas unshift throws an exception in that situation. This seems to have been originally a coincidence. The pp_unshift implementation first makes space for the elements it unshifts (which croaks for a read-only array), then copies the new values into the space thus created. The pp_push implementation, on the other hand, calls av_push() individually on each element; that implicitly croaks, but only one there's at least one element being pushed. The pp_push implementation has subsequently been changed: read-only checking is now done first, but that was done to fix a memory leak. (If the av_push() itself failed, then the new SV that had been allocated for pushing onto the array would get leaked.) That leak fix specifically grandfathered in the acceptance of empty-push-to-readonly-array, to avoid changing behaviour. I'm not fond of the inconsistency betwen push on the one hand and unshift & splice on the other, but I'm disinclined to make empty-push-to-readonly suddenly start throwing an exception after all these years, and it seems best not to extend that exemption-from-exception to the other builtins.
* Use library functions instead of manual TAP in t/io/tell.t.Dmitry Ulanov2017-10-152-51/+45
| | | | | | | | Committer: minor corrections to descriptions. Dmitry Ulanov is now a Perl author. For: RT #132276
View Lorry Controller Status