| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
and hence the 'create' argument is actually 'flags'. Fix code and documentation
that used TRUE or FALSE to use 0 or GV_ADD.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
DB_File was forcing "-llibdb" for all MSWin32 builds. That's an MSVC
thing, so this patch makes it use "-ldb" if the compiler is gcc (e.g.
for Strawberry Perl and friends).
Paul Marquess suggested I send a patch to p5p and will update the
source on CPAN when he has a dev box again.
Message-Id: <1232541093-2247-1-git-send-email-dagolden@cpan.org>
Plus: bump $VERSION.
|
| | |
|
| |
|
|
|
|
|
| |
completely when it moved the allocation logic inside Perl_newXS_flags(). Whilst
Rafael's fix in 29107 correctly plugged my leak, this commit is the actual
correction. (Commits 77004dee2553ce034a8a58b2b2849e3656df46c3 and
c3db7d9213b09a5852dab00368488f63a7625b9e respectively)
|
| |
|
|
| |
Message-Id: <6B717AA7-2972-439F-9B89-669E15353EBC@dwim.org>
|
| |\ |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces pathify_dirspec in vms.c with a new version that better
handles the extended character set.
The [.vms.ext]filespec.t has been adjusted for to support both the
default mode and the extended file spec mode.
This fixes an inconsistency where now vmsify and vmspath will return the
same result for similar input.
Message-ID: <49737F12.6010803@gmail.com>
|
| | |
|
| |
|
|
|
|
|
| |
David patched add-package to support git, but unfortunately introduced
a portability issue for 'cp'; the --archive option isn't supported on
OSX. So, the attached patch changes --archive to it's most equal single
character options that are portable.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
I noticed that Maintainers.pl wasn't listing my modules as having the
CPAN version being canonical. The attached patch fixes this.
It also changes the owner of CPANPLUS::Dist::Build to kwilliams
(as per the PAUSE permissions) and removes CPANPLUS::Dist as a
seperate distribution; it always came with CPANPLUS.
|
| |
|
|
|
|
|
| |
Subject: disabling suidperl in Configure
From: Nicholas Clark <nick@ccl4.org>
Date: Sun, 18 Jan 2009 11:51:39 +0000
Message-ID: <20090118115139.GX2919@plum.flirble.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The NameAliases.txt is an official Unicode database file. It contains
normative names of Unicode code points that any Unicode implementation
is supposed to recognize. These are actually corrections to names that
have been published in UnicodeData.txt erroroneously, but to avoid
breaking code that uses the erroneous name, the folks at Unicode create
these additional ones. (There are about a dozen entries now)
I changed mktables to append these names to Names.pl for use by
charnames. This might break any existing code that relies on that file
being sorted in numerical code point order. But if I added them sorted,
it might break code that relied on there being only one entry per code
point. It's not clear that this file format is considered published and
the api can't change. The point of the file is to go from the name to
the code point anyway, so the order shouldn't matter to any application
using it for its intended purpose.
mktables.list was not regenerated for 5.1, so was out-of-date. The
ordering was random (Linux inode order), so the difference listing for
it is large. I did sort the lists manually and compared them, and they
look ok. I changed mktables to sort the list, so that this problem
doesn't arise again.
I also corrected some typos in mktables, and added a clarifing comment.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Contrary to the comment in the code, h2xs mishandles enums that
contain C++ style comments.
An example of a failing header:
enum {
A = -1, // negative one
// with more comments
B = -2, // negative two
C = -3 // negative two
};
which generates exported constants for 'A' and 'negative'.
The patch is slightly modified from the one by Daniel Burr in
http://bugs.debian.org/320286
|
| | |
|
| | |
|
| |
|
|
|
| |
in perldiag.pod for new warning "Can't fork, trying again in 5 seconds"
added in the parent commit
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This probably needs refinement, possibly a new Configure variable.
|
| |
|
|
|
| |
This notably fixes:
[perl #62484] B::Deparse hangs on called subs with $;_ prototype
|
| |
|
|
|
|
|
|
| |
This patch allows the following to deparse properly:
perl -MO=Deparse -e 'CORE::require "CGI.pm"'
(necessary due to the specific way require() is overriden)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[rt.cpan.org #41827] Can't use $] to select Perl version
The %version hash is initialized with bare numbers for each Perl
version. Unfortunately, the tokenizer will have already eaten trailing
zeros before the fat comma operator is seen, hence the normal
stringification behavior won't have the appropriate affect.
This can be seen by doing something simple like:
perl5.10.0 -MModule::CoreList -e \
'print keys(%{$Module::CoreList::version{$]}})'
which will be empty, since $] is a string not a number. Using $]+0 (to
force numification) will display all of the modules released with 5.10.0.
Either 5.000 and 5.010000 need to be quoted in the %version
initialization or an alias be created, so either 5.01 or "5.010000" (and
hence $]) will work. This latter is probably better to use, trivial patch
(rgs: I added aliases for the %released and %patchlevel hashes too.)
|
| |
|
|
|
| |
It was missing for several versions, including 5.10.0, as reported
by Damyan Ivanov in http://bugs.debian.org/508876
|
| |
|
|
| |
Also bump copyright year.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
(Tweaked by rgs)
Message-ID: <496D3F02.6020204@khwilliamson.com>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The nomenclature is confusing and the CRTL docs even moreso, and
the CRTL implementation seems not to do what the docs say. The
documented default setting is on, which I take to mean that
processing of SYS$POSIX_ROOT is disabled unless you have asked
for it. I've followed this behavior even though the CRTL seems
to report the feature off by default.
Also corrected yet another length error in a related call to
simple_trnlnm.
|
| |
|
|
|
|
|
|
|
| |
The next part in the series: rmsexpand refactor to not use thread context.
Minor fix for VAX included, where VAX was not preserving UNIX syntax on
return for UNIX in.
Message-id: <496DFAFB.4090201@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Attached is a patch for this problem.
The root cause was that S_scan_const() was not recoding to utf8 under
some circumstances when it should be.
I also changed it so that in all places, the flag that indicates the
output is in utf8 is changed from false to true if and only if the
destination is recoded to utf8. One place was skipping this, and then
setting it unconditionally later on.
In one place in the routine, the routine had code to do the recoding
itself. In the other places, it called sv_utf8_upgrade(). I changed it
to call the subroutine in all cases.
I fixed a bug that would appear only on EBCDIC machines where constants
of the form \N{U+....} would have been interpreted as EBCDIC.
And in inspecting the code, I realized there were problems with growing
the scalar value to fit the input. I cleaned those up.
I also added a number of comments to document things I found out, and
changed some existing ones to be more accurate.
Since no one responded to my request for where to put the test cases,
and I couldn't figure out a good place to put them, I added a new test
file, t/uni/lex_utf8.t.
|
| |
|
|
|
|
|
| |
(1) all work done in a new git branch by default
(2) "-n" flag ("no branch") added to get old rsync-friendly behavior
(3) looks in "scripts/" directory as well as "bin/" for executables
(4) patches utils/Makefile.SH instead of utils/Makefile
|
| | |
|
| | |
|
| | |
|
