| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
--------------
0.26 Tue 28 Apr 2015 12:31:17 BST
- There is a new experimental option in bleadperl under which one ought not to use
the op_sibling field directly. Quoting from perlguts.pod:
Starting in version 5.21.2, perls built with the experimental
define C<-DPERL_OP_PARENT> add an extra boolean flag for each op,
C<op_moresib>. When not set, this indicates that this is the last op in an
C<OpSIBLING> chain. This frees up the C<op_sibling> field on the last
sibling to point back to the parent op. Under this build, that field is
also renamed C<op_sibparent> to reflect its joint role. The macro
C<OpSIBLING(o)> wraps this special behaviour, and always returns NULL on
the last sibling. With this build the C<op_parent(o)> function can be
used to find the parent of any op. Thus for forward compatibility, you
should always use the C<OpSIBLING(o)> macro rather than accessing
C<op_sibling> directly.
Thanks to Reini Urban for the patch.
|
|
--------------
2.43 2015-04-26 Make segfault go away on Windows
|
|
--------------
0.26
- fix tests for perl 5.21.7 (change to nulled COPs) (RT#100508, Father
Chrysostomos)
|
|
- Drop patch-CVE-2014-8964 (now included)
(upstream)
- Update to 8.37
Version 8.37 28-April-2015
--------------------------
1. When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
for those parentheses to be closed with whatever has been captured so far.
However, it was failing to mark any other groups between the hightest
capture so far and the currrent group as "unset". Thus, the ovector for
those groups contained whatever was previously there. An example is the
pattern /(x)|((*ACCEPT))/ when matched against "abcd".
2. If an assertion condition was quantified with a minimum of zero (an odd
thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
3. If a pattern in pcretest input had the P (POSIX) modifier followed by an
unrecognized modifier, a crash could occur.
4. An attempt to do global matching in pcretest with a zero-length ovector
caused a crash.
5. Fixed a memory leak during matching that could occur for a subpattern
subroutine call (recursive or otherwise) if the number of captured groups
that had to be saved was greater than ten.
6. Catch a bad opcode during auto-possessification after compiling a bad UTF
string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
UTF with NO_UTF_CHECK is documented as having an undefined outcome.
7. A UTF pattern containing a "not" match of a non-ASCII character and a
subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
8. When a pattern is compiled, it remembers the highest back reference so that
when matching, if the ovector is too small, extra memory can be obtained to
use instead. A conditional subpattern whose condition is a check on a
capture having happened, such as, for example in the pattern
/^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
setting the highest backreference number. This mattered only if pcre_exec()
was called with an ovector that was too small to hold the capture, and there
was no other kind of back reference (a situation which is probably quite
rare). The effect of the bug was that the condition was always treated as
FALSE when the capture could not be consulted, leading to a incorrect
behaviour by pcre_exec(). This bug has been fixed.
9. A reference to a duplicated named group (either a back reference or a test
for being set in a conditional) that occurred in a part of the pattern where
PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
to be incorrectly calculated, leading to overwriting.
10. A mutually recursive set of back references such as (\2)(\1) caused a
segfault at study time (while trying to find the minimum matching length).
The infinite loop is now broken (with the minimum length unset, that is,
zero).
11. If an assertion that was used as a condition was quantified with a minimum
of zero, matching went wrong. In particular, if the whole group had
unlimited repetition and could match an empty string, a segfault was
likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
assertions to be quantified, but not if they are being used as conditions,
so the above pattern is faulted by Perl. PCRE has now been changed so that
it also rejects such patterns.
12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
failed to allow the zero-repeat case if pcre2_exec() was called with an
ovector too small to capture the group.
13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
Red Hat Product Security:
(a) A crash if /K and /F were both set with the option to save the compiled
pattern.
(b) Another crash if the option to print captured substrings in a callout
was combined with setting a null ovector, for example \O\C+ as a subject
string.
14. A pattern such as "((?2){0,1999}())?", which has a group containing a
forward reference repeated a large (but limited) number of times within a
repeated outer group that has a zero minimum quantifier, caused incorrect
code to be compiled, leading to the error "internal error:
previously-checked referenced subpattern not found" when an incorrect
memory address was read. This bug was reported as "heap overflow",
discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
CVE-2015-2325.
23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
call within a group that also contained a recursive back reference caused
incorrect code to be compiled. This bug was reported as "heap overflow",
discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
number CVE-2015-2326.
24. Computing the size of the JIT read-only data in advance has been a source
of various issues, and new ones are still appear unfortunately. To fix
existing and future issues, size computation is eliminated from the code,
and replaced by on-demand memory allocation.
25. A pattern such as /(?i)[A-`]/, where characters in the other case are
adjacent to the end of the range, and the range contained characters with
more than one other case, caused incorrect behaviour when compiled in UTF
mode. In that example, the range a-j was left out of the class.
26. Fix JIT compilation of conditional blocks, which assertion
is converted to (*FAIL). E.g: /(?(?!))/.
27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
discovered by the LLVM fuzzer.
28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
when this assertion was used as a condition, for example (?(?!)a|b). In
pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
error about an unsupported item.
29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
possessification code could take exponential time to complete. A recursion
depth limit of 1000 has been imposed to limit the resources used by this
optimization.
30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
because \S ensures they are all in the class. The code for doing this was
interacting badly with the code for computing the amount of space needed to
compile the pattern, leading to a buffer overflow. This bug was discovered
by the LLVM fuzzer.
31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
other kinds of group caused stack overflow at compile time. This bug was
discovered by the LLVM fuzzer.
32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
between a subroutine call and its quantifier was incorrectly compiled,
leading to buffer overflow or other errors. This bug was discovered by the
LLVM fuzzer.
33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
assertion after (?(. The code was failing to check the character after
(?(?< for the ! or = that would indicate a lookbehind assertion. This bug
was discovered by the LLVM fuzzer.
34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
a fixed maximum following a group that contains a subroutine reference was
incorrectly compiled and could trigger buffer overflow. This bug was
discovered by the LLVM fuzzer.
35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
caused a stack overflow instead of the diagnosis of a non-fixed length
lookbehind assertion. This bug was discovered by the LLVM fuzzer.
36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
(e.g. /(?<=\Ka)/) could make pcregrep loop.
37. There was a similar problem to 36 in pcretest for global matches.
38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
and a subsequent item in the pattern caused a non-match, backtracking over
the repeated \X did not stop, but carried on past the start of the subject,
causing reference to random memory and/or a segfault. There were also some
other cases where backtracking after \C could crash. This set of bugs was
discovered by the LLVM fuzzer.
39. The function for finding the minimum length of a matching string could take
a very long time if mutual recursion was present many times in a pattern,
for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
method has been implemented. This infelicity was discovered by the LLVM
fuzzer.
40. Static linking against the PCRE library using the pkg-config module was
failing on missing pthread symbols.
|
|
When building in pkg_comp, this option cause the real UID/GID to
be used at install time within the chroot. But the user that exists
in the root filesystem may not exist in the chroot, causing an
installation failure.
|
|
Added devel/p5-Module-Manifest-Skip version 0.23
|
|
devel/p5-Module-Install-AuthorRequires.
Modules often have optional requirements, for example dependencies that are
useful for (optional) tests, but not required for the module to work
properly.
Usually you want all developers of a project to have these optional modules
installed. However, simply telling everyone or printing diagnostic messages
if optional dependencies are missing often isn't enough to make sure all
authors have all optional modules installed.
|
|
NOTE: This module is mostly intended for module packaging frameworks to
share a common, up-to-date MANIFEST.SKIP base. For example,
Module::Install::ManifestSkip, uses this module to get the actual SKIP
content. However this module may be useful for any module author.
CPAN module authors use a MANIFEST.SKIP file to exclude certain well known
files from getting put into a generated MANIFEST file, which would cause
them to go into the final distribution package.
The packaging tools try to automatically skip things for you, but if you
add one of your own entries, you have to add all the common ones
yourself. This module attempts to make all of this boring process as simple
and reliable as possible.
Module::Manifest::Skip can create or update a MANIFEST.SKIP file for
you. You can add your own entries, and it will leave them alone. You can
even tell it to not skip certain entries that it normally skips, although
this is rarely needed.
|
|
|
|
|
|
|
|
|
|
This module provides standardized logging facilities using the
Log::Message module.
|
|
|
|
---------------
0.007 2015-04-27
- separate loading and merging of configfile content
- ensure order of multiple loaded config files
- add support for merging deep structures in config files
- eval all test-libraries to be aware of mistakes
|
|
---------------
0.017 2015-04-27
- add irc channel and mailing list to meta data
- apply fix regarding "Cwd::abs_path is not portable" from jddurand
|
|
|
|
|
|
Test::Spelling lets you check the spelling of a POD file, and report its
results in standard Test::More fashion. This module requires a spellcheck
program such as spell, aspell, ispell, or hunspell.
|
|
|
|
devel/p5-Module-Install-ManifestSkip.
This module generates a MANIFEST.SKIP file for you (using
Module::Manifest::Skip) that contains the common files that people do not
want in their MANIFEST files. The SKIP file is generated each time that you
(the module author) run Makefile.PL.
You can add your own custom entries at the top of the MANIFEST file. Just
put a blank line after your entries, and they will be left alone.
This module also adds 'MANIFEST' to the clean_files() list so that make
clean will remove your MANIFEST.
|
|
|
|
Module::Install::GithubMeta is a Module::Install extension to include
GitHub http://github.com meta information in META.yml.
It automatically detects if the distribution directory is under git version
control and whether the origin is a GitHub repository and will set the
repository and homepage meta in META.yml to the appropriate URLs for
GitHub.
|
|
|
|
Test::NoTabs lets you check the presence of tabs in your perl code.
It reports its results in standard Test::Simple fashion:
use Test::NoTabs tests => 1;
notabs_ok( 'lib/Module.pm', 'Module is tab free');
|
|
corrected, thanks wiz@.
|
|
|
|
2015-04-20 meld 3.13.1
======================
Features:
* Previously, Meld could show very different results in file vs. folder
comparisons when the files differed in line endings. These are now much
more consistent.
* In folder comparisons, applying filters now also normalises line
endings (Kai Willadsen)
* In a file comparison, if the files-are-identical notification is shown
when files differ in line endings, this now mentioned (Kai Willadsen)
* There is a new preferences controlling whether to apply text filters
during folder comparisons, defaulting to on, which also controls line
ending normalisation (Kai Willadsen)
* Help documentation has been updated with details of how text filters
are applied in folder comparison (Kai Willadsen)
* Folder comparisons will now show an identical notification similar to the
one used in file comparison (Kai Willadsen)
* The "New blank comparion" button now works for folder comparisons as well
as file ones (Kai Willadsen)
* In folder comparisons, the expansion state of the tree is now remembered
when you collapse and re-expand a row (Kai Willadsen)
Fixes:
* Install fixes (oco)
* Code style fixes (Sandro Bonazzola)
* Better support RTL locales by flipping icons and panes consistently (Kai
Willadsen)
* Fixes for file encoding when saving with bad or missing encodings (Kai
Willadsen)
* More consistent dialog handling and appearance (Kai Willadsen)
* Deprecation updates and compatibility fixes (Kai Willadsen)
* Fix bad comparison offset when multiple line breaks occurred on a single
line (don't ask) (Kai Willadsen)
* Unicode fixes for file change notifications (Kai Willadsen)
* Warnings (such as deprecation warnings) are now explicitly silenced in
stable Meld (Kai Willadsen)
* Folder actions are now disabled while Meld is still scanning folders (Kai
Willadsen)
* Fix some command line handling for ambiguous relative paths and invalid
URIs (Kai Willadsen)
* Fix updating the comparison map when a file is updated within Meld (Kai
Willadsen)
Translations:
* Anders Jonsson (sv)
* Cheng-Chia Tseng (zh_TW)
* Christian Kirbach (de)
* Daniel Mustieles (es)
* Jordi Mas (ca)
* Marek Černocký (cs)
* Matej Urbančič (sl)
* Piotr Drąg (pl)
* Samir Ribic (bs)
* Tibor Kaputa (sk)
|
|
|
|
Experimental LaTeX3 concepts
|
|
-- Drop patch-aa, was commented as:
------
Until the source catches up to the current Perl API, we need PERL_POLLUTE
to look like an older perl.
------
(upstream)
-- Update 1.2.2 (imported to pkgsrc in 1999) to 1.4.1
--------------------------------------------------
2000-09-19 Leif Hedstrom <leif@perldap.org>
* Conn.pm (update): Bug fix to allow us to delete() an attribute,
call update(), and then add new values (or the same values...) to
the entry again.
2000-09-19 Leif Hedstrom <leif@perldap.org>
* Entry.pm (DESTROY): Bug fix from daniel.hams@db.com (Daniel
Hams) to avoid warnings from Apache and mod_perl.
2000-09-13 Leif Hedstrom <leif@perldap.org>
* Utils.pm (askPassword): Oops, stupid typo here, should be
"unless $prompt" of course...
2000-09-13 Leif Hedstrom <leif@perldap.org>
* Entry.pm (isDeleted): Removed a test which made this function
not working at all... :)
2000-09-13 Leif Hedstrom <leif@perldap.org>
* Removed an if defined() to avoid warnings with Perl v5.6.
2000-06-24 Wolfram Schmidt <wschmidt@decefix.iao.fhg.de>
* Entry.pm (FIRSTKEY): Fix bug for deleting all attributes and calling
keys.
2000-05-30 Kevin McCarthy <kevin@perldap.org>
* Makefile.PL: Added fix so API.xs compiles under Perl 5.6
(POLLUTE=>1)
2000-05-30 Leif Hedstrom <leif@perldap.org>
* Lots of small fixes...
1999-09-07 Leif Hedstrom <leif@perldap.org>
* API.xs (avref2charptrptr): Fixed potential core dump, if the
argument passed wasn't a proper array.
(avref2berptrptr): Ditto.
1999-09-06 Leif Hedstrom <leif@perldap.org>
* Conn.pm (search): Removed $res and $resv, set the internal data
element directly.
(searchURL): Ditto.
1999-08-25 John Kristian <kristian@netscape.com>
* Entry.pm (printLDIF): Bug fix.
* LDIF.pm: Cleaned out memory leaks.
1999-08-24 Leif Hedstrom <leif@netscape.com>
* Merged v1.3.x into trunk, tagged it as v1.4, and released it!
1999-08-19 Leif Hedstrom <leif@netscape.com>
* Changed internal version numbering again, just called this plain
v1.4.
* Entry.pm (FIRSTKEY): Bug fix, we'd crap out if there are no
attributes in the returned entry.
(NEXTKEY): Ditto.
1999-08-18 Leif Hedstrom <leif@netscape.com>
* Set version number to v1.4! Woohoo! Also tagged it as v1.3.4,
last "development" release.
1999-08-17 Leif Hedstrom <leif@netscape.com>
* Makefile.PL: Fixes for Windows/NT, cleaned out some code etc.
(MY::postamble): Support for "make html".
* MANIFEST: Updated with all new files etc.
* test.pl: Renamed to oldtest.pl, to avoid "make test" to fail.
1999-08-16 Kevin McCarthy <kmccarth@perldap.org> and Leif Hedstrom
* API.xs: Cleaned most all the memory allocation changes, we are
changing it to use the LDAP_OPT_MEMALLOC_FN_PTRS option in the
C-SDK instead (much cleaner!).
(perldap_init): New function, set up the memory management
handlers. This is called when the API module is loaded.
(perldap_malloc): New function, our memory management method(s).
(perldap_calloc): Ditto.
(perldap_realloc): Ditto.
(perldap_free): Ditto.
1999-08-16 Kevin McCarthy <kmccarth@perldap.org>
* API.xs: Cleaned up prototypes, changed strdup() to use a
Perl'ified version, change a number of free()'s to use Safefree.
(ldap_value_free_perl): New function, similar to
ldap_mods_free_perl(), to avoid memory problems (on NT and
ActivePerl primarily).
(StrDup): New function, to handle strdup() calls in a safe way.
(ber_bvfree_perl): Ditto.
(ber_bvecfree_perl): Ditto.
1999-08-15 Leif Hedstrom <leif@netscape.com>
* API.xs (ldap_mods_free_perl): Modified version of
ldap_mods_free(), which uses Perl native free method instead of
the things from the LDAP SDK. This fixes some nasty issues with
Windows/NT and ActiveState Perl. Woohoo!!!
1999-08-14 Leif Hedstrom <leif@netscape.com> and Kevin McCarthy
* Entry.pm (setValues): Implemented bug fix for bug id 7131, where
the "_save_" structures weren't set properly when using setValues().
1999-08-14 Kevin McCarthy <kmccarth@perldap.org>
* Conn.pm (update): Rewrote to optimize add/remove vs replace
operations. Basically, we'll try to do whatever seems to be the
smallest amount of work for the LDAP server now.
1999-08-13 Leif Hedstrom <leif@netscape.com>
* Makefile.PL: Cleaned up code, and added support for linking in
the missing libraries need for some missing symbols.
1999-08-13 Michelle Wyner <mwyner@netscape.com>
* Entry.pm: Updated documentation, and cleaned it up.
* Conn.pm: Ditto.
1999-08-12 Leif Hedstrom <leif@netscape.com>
* Entry.pm (move): Changed name, was rename(), is now move().
1999-08-10 Leif Hedstrom <leif@netscape.com>
* Entry.pm (setValues): Renamed, used to be setValue(), which is
now an alias to setValues().
(getValues): New method, to get the array of values.
(STORE): Fixed tests around DN handling, making sure it's not
treated as an array. I also optimized a couple of tests, since we
now filter out "DN" earlier in the funtion(s).
(attrModified): Ditto.
(attrClean): Ditto.
(unRemove): Ditto.
(removeValue): Ditto.
(addValue): Ditto.
1999-08-08 Leif Hedstrom <leif@netscape.com> and Kevin McCarthy
* Entry.pm (setValue): Remove _delete_ flag, if set.
* Conn.pm (close): Fixed memory leak, moved code from the DESTROY
method over here.
(DESTROY): Call the close() method.
(getErrorCode): We now return LDAP_SUCCESS if there is no LDAP
connection handle.
(getErrorString): Ditto.
* Entry.pm (STORE): Bug fix for large attribute sets.
(attrModified): Ditto.
(removeValue): Ditto.
(addValue): Ditto.
(EXISTS): Fix for bug 4368, cleaning up the code, and avoid the
double calls.
1999-08-06 Leif Hedstrom <leif@netscape.com> and Kevin McCarthy
* API.xs: Added some more tests around free() statements. These
are most likely never triggered, but better safe than sorrow (and
the overhead of testing this is insignificant).
* Conn.pm (browse): Added this function, to make it easy to browse
an entry.
(compare): Compare an attribute value against a DN/entry, without
having to do the search.
* Entry.pm (removeValue): Fixed loop bug.
(addValue): Ditto.
(hasValue): Ditto.
(matchValue): Fixed loop bug, and also missing normalization in
half of the case statement.
(rename): Added this new method, to rename attributes.
(copy): Added, to copy attributes.
* Merged v1.2.3 with v1.3 branch.
1999-08-06 Kevin McCarthy <kmccarth@perldap.org>
* Entry.pm (addDNValue): Bug fix, index for norm was wrong.
* Entry.pm (size): Optimzied for performance.
1999-07-25 Kevin McCarthy <kmccarth@perldap.org>
* API.xs: Fixed memory allocation problems in parsing and
generating the LDAPMods structure.
1999-06-22 Leif Hedstrom <leif@netscape.com>
* Conn.pm (add): Fixed bug 3342, thanks to Kevin McCarthy for
debugging this, and providing a patch. This fixes the problem with
adding new entries that has binary data.
1999-03-23 Leif Hedstrom <leif@netscape.com>
* Changed versioning numbers for all .pm files.
1999-03-22 Leif Hedstrom <leif@netscape.com>
* Entry.pm: Removed all _self_obj_ stuff...
* Conn.pm: Ditto.
* Conn.pm: Cleanup in use statements, and "use strict".
(search): Avoid warnings of uninitialized variables.
(searchURL): Ditto.
(modifyRDN): Bugfix, we did not update the appropriate DN in the
self object (very minor...).
* Entry.pm: Cleanup in use statements, and "use strict".
(BEGIN): Added this initializer, to use the new LDIF module.
(STORE): Fixed bug where we would not ignore the internal instance
variables properly.
* Utils.pm: Cleanup in all use statements, and "use strict". Also
enforces the VERSION control feature.
* Merged v1.2.1 to devel-branch-1_3, and tagged v1.3.1.
|
|
includes Test::use:ok since 1.001010.
PKGREVISION++.
(For BUILD_DEPENDS, assuming Test::use:ok will be removed sometime.)
|
|
binary here to execute it.
|
|
are necessary to make the package work and avoid any confusion on the part
of the user. More changes for this package forthcoming.
|
|
|
|
|
|
+ Version 2.12 (21.04.2015)
- This is a fix release for 2.11; the memory optimization with __slots__ on
Coord and AST nodes didn't take weakrefs into account, which broke cffi and
its many dependents (iseue #76). Fixed by adding __weakref__ to __slots__.
+ Version 2.11 (21.04.2015)
- Add support for C99 6.5.3.7 p7 - qualifiers within array dimensions in
function declarations. Started with issue #21 (reported with initial patch
by Robin Martinjak).
- Issue #27: bug in handling of unified wstring literals.
- Issue #28: fix coord reporting for 'for' loops.
- Added ``examples/using_gcc_E_libc.py`` to demonstrate how ``gcc -E`` can
be used instead of ``cpp`` for preprocessing.
- Pull request #64: support keywords like const, volatile, restrict and static
in dimensions in array declarations.
- Reduce memory usage of AST nodes (issue #72).
- Parsing order of nested pointer declarations fixed (issue #68).
|
|
--------------
Version 1.72b:
--------------
- Fixed a glitch in non-x86 install, spotted by Tobias Ospelt.
- Added a minor safeguard to llvm_mode Makefile following a report from
Kai Zhao.
--------------
Version 1.71b:
--------------
- Fixed a bug with installed copies of AFL trying to use QEMU mode. Spotted
by G.M. Lime.
- Added last path / crash / hang times to fuzzer_stats, suggested by
Richard Hipp.
- Fixed a typo, thanks to Jakub Wilk.
|
|
------------------
2.000001 - 2015-04-24
- fix generating invalid package names with single colons when abbreviating
long package names (RT#103310)
- don't run module interaction tests for user installs
|
|
-------------
2.1 Fri 24 Apr 2015 20:29:12 BST
- Another bleadperl fix
https://rt.cpan.org/Public/Bug/Display.html?id=101037
|
|
-----------------------------------------
version 1.34 at 2015-04-25 15:23:56 +0000
-----------------------------------------
Release engineering for 1.34
Date : 2015-04-17 17:19:35 +0000
Merge pull request #19 from wolfsage/topic/various-fixes
Topic/various fixes
Date : 2015-04-17 07:10:05 +0000
Specific patch for 5.005
Date : 2015-04-17 06:58:28 +0000
Specific patches for 5.005_02 and 5.005_01
Date : 2015-04-17 06:14:25 +0000
Allow building of 5.005_0[34] on linux.
Date : 2015-04-17 06:10:44 +0000
Updated hints files, necessary to build older Perls
|
|
|
|
|
|
programming languages. The bridge is intended to be fully bidirectional,
allowing the Python programmer to take full advantage of the power provided by
various Objective-C based toolkits and the Objective-C programmer transparent
access to Python based functionality.
|
|
* "diff-highlight" (in contrib/) used to show byte-by-byte
differences, which meant that multi-byte characters can be chopped
in the middle. It learned to pay attention to character boundaries
(assuming the UTF-8 payload).
Also contains typofixes, documentation updates and trivial code
clean-ups.
|
|
-------------------
0.35 2015-04-06 22:20 UTC
+ Fix : The module could end being disabled in one thread if it was
first loaded in another thread and that thread was immediately
terminated. This is now fixed and should address test failures
of t//09-load-threads.t and t/42-threads-global.t.
0.34 2015-04-02 19:50 UTC
+ Chg : The new environment variable to enable thread tests on older
perls is PERL_FORCE_TEST_THREADS. Note that this variable
should only be turned on by authors.
+ Fix : [RT #100068] : add link to historical tchrist post
The link has been added to the documentation. Thanks Olivier
Mengué for reporting.
+ Fix : Segfaults when the module is loaded by several threads (or
Windows emulated processes) ran in parallel.
+ Fix : Update the Windows ActivePerl + gcc 3.4 workaround for
ExtUtils::MakeMaker 7.04. Thanks Christian Walde for reporting
and feedback on this issue.
+ Fix : Be really compatible with the optional OP_PARENT feature.
+ Tst : $ENV{$Config{ldlibpthname}} is now preserved on all platforms,
which will address failures of t/41-threads-teardown.t and
t/50-external.t with unusual compilers (like icc) that link all
their compiled objects to their own libraries.
|
|
-------------------
0.22 Sun 15 Dec 2013 17:08:35 GMT
- Prevent return from being optimised away by newer (>= 5.19.7) Perls.
This is a patch supplied by @wolfsage: see
https://github.com/robinhouston/Want/pull/1
0.23 Mon 24 Mar 2014 00:28:36 GMT
- Accommodate a bleadperl change to the optree, made in
7d3c8a6837b55fff0e6294ebf8c94a1601367c76.
This is bug #94086 for Want, and bug #121342 for perl5.
0.24 Tue 2 Dec 2014 10:22:39 GMT
- Accommodate another bleadperl change. Patch provided by Father Chrysostomos at
https://rt.cpan.org/Public/Bug/Display.html?id=100626
0.25 Wed 10 Dec 2014 19:31:03 GMT
- Add support for the new OP_MULTIDEREF
Perl has a new op, added as a performance optimisation
in fedf30e1c349130b23648c022f5f3cb4ad7928f3, to
represent a sequence of array/hash dereferences. This
patch adds support for the new op.
|
|
-------------------
0.57 2015-04-17 15:20 UTC
+ Chg : The new environment variable to enable thread tests on older
perls is PERL_FORCE_TEST_THREADS. Note that this variable
should only be turned on by authors.
+ Fix : Segfaults when the module is loaded by several threads (or
Windows emulated processes) ran in parallel.
+ Fix : Segfaults when the module is loaded in a thread, which spawns
itself a new thread, and that child thread outlives its parent.
+ Fix : Small memory leaks of structures required for thread safety.
+ Fix : Update the Windows ActivePerl + gcc 3.4 workaround for
ExtUtils::MakeMaker 7.04. Thanks Christian Walde for reporting
and feedback on this issue.
+ Tst : The global destruction test will now be exercised on any perl
that has DEBUGGING set.
+ Tst : Optional capturing tests in t/17-ctl.t that were only run when
Capture::Tiny was present were converted to an IPC::Open3
based helper and will now be run everywhere.
0.56 2015-03-11 15:15 UTC
+ Fix : [RT #101410] : Install fails in blead
Even though the change that caused this error was reverted from
blead, lvalue uses of ERRSV have been removed from this module
so that there will be no breakage when this change is possibly
reintroduced in the following months.
Thanks Dave Rolsky for reporting.
+ Tst : $ENV{$Config{ldlibpthname}} is now preserved on all platforms,
which will address failures of t/17-ctl.t with unusual
compilers (like icc) that link all their compiled objects to
their own libraries.
+ Tst : The global destruction test is now only run on perl 5.13.4 and
higher, and only if either Perl::Destruct::Level is installed
or PERL_DESTRUCT_LEVEL is set and the perl is a debugging perl.
This will solve rare crashes of t/15-self.t on perl 5.13.3 and
older.
|
|
--------------
0.18 2015-02-24
- Skip the taint test if Perl was compiled without taint support.
RAZ++
- Changed use of "use vars" to "our"
- Added strict and warnings to PREREQ_PM
|
|
- Fix logic in sub DESTROY for when children are/are not
present. Reported by astortz. See
https://github.com/stevan/tree-simple/issues/8.
1.24 Sat Sep 6 09:27:00 2014
- Abandon Test::Version and hence delete t/version.t. Putting
version.t in xt/author/ is not a solution, because
Test::Version has problems with Test::EOL and Test::Builder.
Thanx to Kent Fredric for the github issue which started me
investigating this issue.
|
