| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Because if we're running under a Unix shell, the path separator is
likely to meet the expectations of Unix shell scripts better if it's
the Unix ':' rather than the VMS '|'. There is no change when
running under DCL.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
For those %ENV elements based on the CRTL environ array, we've
always preserved case when setting them but done look-ups only
after upcasing the key first, which makes lower- or mixed-case
entries go missing.
So make them consistently case-preserved and in the docs
distinguish this behavior from the case-blind behavior of keys
for %ENV entries based on logical namees and DCL symbols, which
remains unchanged.
|
| |
|
|
|
| |
Remove some woefully out-of-date and/or incorrect material and fix
a few other nits.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The default for populating %ENV on VMS is from logical names
first and the CRTL environ array second unless overridden by
setting PERL_ENV_TABLES. That's a reasonable default for DCL,
but not quite right when running under bash as exports under bash
might end up hidden behind logical names. So reverse the default
order when GNV$UNIX_SHELL is set.
Also stop mentioning that setenv() may not be present in the CRTL
since it is present for VMS versions 7.0 and later and those are
the only ones we support.
|
| |
|
|
|
|
| |
This makes the uses of this consistent in our pods. Also changed one
use of the word 'buffer' into 'string', the latter being more
appropriate.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This makes many documents more consistent in their pod formatting. Don't trim
blank lines between verbatim blocks and =item, as removing them makes the (raw)
pod harder to read.
|
| | |
|
| |
|
|
|
|
|
| |
# New Ticket Created by (Peter J. Acklam)
# Please include the string: [perl #81906]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=81906 >
|
| |
|
|
|
|
|
|
| |
As Charles Lane's piping code reaches its 10-year anniversary, it's
time to bump up the default to something slightly more appropriate
for modern systems. In addition to other benefits, this fixes test
failures when a test script outputs a large amount of text on one
line (e.g., t/re/reg_posixcc.t).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
These are all in the pod/ directory, and only the first is a code fix.
There was also a single lingering ISO 8859-1 encoding that missed the
UTF-8 upconvert. The rest are cleanups for typos, some of which seem
to have been around for a rather long time: spelling errors, incorrect
possessives, and extra, missing, or duplicated words.
If you actually read through, I bet you'll realize what sparked this. :)
--tom
Signed-off-by: Abigail <abigail@abigail.be>
|
| |
|
|
| |
Signed-off-by: Abigail <abigail@abigail.be>
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
name. That should help you with what to put in the delta file.
I forgot to indicate in the file that the DECC$FILENAME_UNIX_REPORT
feature also activates the PERL_VMS_POSIX_EXIT mode.
|
| | |
|
| |
|
|
|
|
| |
in VMS, it seems. Maybe the vms/descrip_mms.template
needs to be changed?
p4raw-id: //depot/perl@20832
|
|
|
p4raw-id: //depot/perl@20826
|
