Upstream changes:
1.43 Fri Oct 23 14:00 2015
- Update copyright + version correctly everywhere
1.42 Fri Oct 23 13:30 2015
- Allow get_and_set callback to return an empty list
which means "no change". This allows atomic
"get, and set if not present" type action, but
without resetting the expiry time on each get.
This is basically the same as using the read_cb
1.41 Thu Aug 29 15:30 2013
- Actually reuse deleted slots. Meant that if
you used ->remove() a lot, we would re-organise
cache more than needed
- Include typo and meta patches from dsteinbrunner
Upstream changes:
1.30
New Features
- first() arguments are now consistent with grep(), so now you can
supply single non-ref scalar to it (xenu)
Incompatible Changes
- Removed smartmatch from first() and grep(). Now these methods have
consistent behaviour under all perl versions and their code is much
cleaner (xenu)
Docs
- Fixed typo reported by myfwhite on annocpan (xenu)
1.29
Fix
- Suppress smartmatch deprecation warnings in perls >= 5.18 (xenu)
"Include what you use" means this: for every symbol (type, function
variable, or macro) that you use in foo.cc, either foo.cc or foo.h
should #include a .h file that exports the declaration of that symbol.
The include-what-you-use tool is a program that can be built with the
clang libraries in order to analyze #includes of source files to find
include-what-you-use violations, and suggest fixes for them.
The main goal of include-what-you-use is to remove superfluous #includes.
It does this both by figuring out what #includes are not actually needed for
this file (for both .cc and .h files), and replacing #includes with
forward-declares when possible.
pkgsrc changes:
- convert to egg.mk (no functional changes intended)
- use MASTER_SITE_PYPI
- update HOMEPAGE (sf.net project page seems not available ATM while the
distfiles are fetchable from sf.net)
- minor cosmetic fixes
Changes:
Version 2.0.6 -
---------------------------
- Fixed a bug in Each when multiple Optional elements are present.
Thanks for reporting this, whereswalden on SO.
- Fixed another bug in Each, when Optional elements have results names
or parse actions, reported by Max Rothman - thank you, Max!
- Added optional parseAll argument to runTests, whether tests should
require the entire input string to be parsed or not (similar to
parseAll argument to parseString). Plus a little neaten-up of the
output on Python 2 (no stray ()'s).
- Modified exception messages from MatchFirst and Or expressions. These
were formerly misleading as they would only give the first or longest
exception mismatch error message. Now the error message includes all
the alternatives that were possible matches. Originally proposed by
a pyparsing user, but I've lost the email thread - finally figured out
a fairly clean way to do this.
- Fixed a bug in Or, when a parse action on an alternative raises an
exception, other potentially matching alternatives were not always tried.
Reported by TheVeryOmni on the pyparsing wiki, thanks!
- Fixed a bug to dump() introduced in 2.0.4, where list values were shown
in duplicate.
Version 2.0.5 -
---------------------------
- (&$(@#&$(@!!!! Some "print" statements snuck into pyparsing v2.0.4,
breaking Python 3 compatibility! Fixed. Reported by jenshn, thanks!
Version 2.0.4 -
---------------------------
- Added ParserElement.addCondition, to simplify adding parse actions
that act primarily as filters. If the given condition evaluates False,
pyparsing will raise a ParseException. The condition should be a method
with the same method signature as a parse action, but should return a
boolean. Suggested by Victor Porton, nice idea Victor, thanks!
- Slight mod to srange to accept unicode literals for the input string,
such as "[а-яА-Я]" instead of "[\u0430-\u044f\u0410-\u042f]". Thanks
to Alexandr Suchkov for the patch!
- Enhanced implementation of replaceWith.
- Fixed enhanced ParseResults.dump() method when the results consists
only of an unnamed array of sub-structure results. Reported by Robin
Siebler, thanks for your patience and persistence, Robin!
- Fixed bug in fourFn.py example code, where pi and e were defined using
CaselessLiteral instead of CaselessKeyword. This was not a problem until
adding a new function 'exp', and the leading 'e' of 'exp' was accidentally
parsed as the mathematical constant 'e'. Nice catch, Tom Grydeland - thanks!
- Adopt new-fangled Python features, like decorators and ternary expressions,
per suggestions from Williamzjc - thanks William! (Oh yeah, I'm not
supporting Python 2.3 with this code any more...) Plus, some additional
code fixes/cleanup - thanks again!
- Added ParserElement.runTests, a little test bench for quickly running
an expression against a list of sample input strings. Basically, I got
tired of writing the same test code over and over, and finally added it
as a test point method on ParserElement.
- Added withClass helper method, a simplified version of withAttribute for
the common but annoying case when defining a filter on a div's class -
made difficult because 'class' is a Python reserved word.
Version 2.0.3 -
---------------------------
- Fixed escaping behavior in QuotedString. Formerly, only quotation
marks (or characters designated as quotation marks in the QuotedString
constructor) would be escaped. Now all escaped characters will be
escaped, and the escaping backslashes will be removed.
- Fixed regression in ParseResults.pop() - pop() was pretty much
broken after I added *improvements* in 2.0.2. Reported by Iain
Shelvington, thanks Iain!
- Fixed bug in And class when initializing using a generator.
- Enhanced ParseResults.dump() method to list out nested ParseResults that
are unnamed arrays of sub-structures.
- Fixed UnboundLocalError under Python 3.4 in oneOf method, reported
on Sourceforge by aldanor, thanks!
- Fixed bug in ParseResults __init__ method, when returning non-ParseResults
types from parse actions that implement __eq__. Raised during discussion
on the pyparsing wiki with cyrfer.
pkgsrc changes:
o Get rid of VERSION variable and other PKGNAME hard-coding and use
make(1) ``:tl'' modifier instead (no functional change intended)
o Use MASTER_SITE_PYPI instead of the full pypi URL.
Changes:
0.10.0
------
o Various misc bug fixes and improvements
4.0.6 Removed a file x.py accidentally entered in the tarball (2015/12/11)
4.0.5 Documented a quirk signaled by David Goldstein when writing decorators
for functions with keyword arguments. Avoided copying the globals,
as signaled by Benjamin Peterson (2015/12/09)
4.0.4 Included a patch from Zev Benjamin: now decorated functions play well
with cProfile (2015/09/25)
4.0.3 Added a warning about the memoize example, as requested by Robert
Buchholz (2015/09/25)
and earlier, when run in daemon mode, does not properly handle the file
descriptor for the logger, which allows remote attackers to cause a denial of
service (abort) via an invalid request.
Bump pkgrevision.
Go packages now define a set of files to buildlink in their buildlink3.mk.
go-packages.mk no longer looks in ${PREFIX}/gopkg during the build. This
should also fix the spurious issues with rebuilds of .a files during bulk
builds of Go packages.
Remove readline dependency fossil now uses the linenoise library
(embedded src).
Install manpage, license and linenoise license.
Changelog:
* Make the fossil clean command undoable for files less than 10MiB.
* Update internal Unicode character tables, used in regular expression
handling, from version 7.0 to 8.0.
* Add the new amend command which is used to modify tags of a "check-in".
* Fix bug in import command, handling version 3 of the svndump format for
subversion.
* Add the all cache command.
* TH1 enhancements:
Add minimal [lsearch] command. Only exact case-sensitive matching is
supported.
Add the [glob_match], [markdown], [dir], and [encode64] commands.
Add the [tclIsSafe] and [tclMakeSafe] commands to the Tcl integration
subsystem.
Add 'double', 'integer', and 'list' classes to the [string is] command.
* Add the --undo option to the diff command.
* Build-in Antirez's "linenoise" command-line editing library
for use with the fossil sql command on Unix platforms.
* Add stash cat as an alias for the stash show command.
* Automatically pull before fossil merge when auto-sync is enabled.
* Fix --hard option to fossil mv and fossil rm to enable them to work properly
with certain relative paths.
* Change the mimetype for ".n" and ".man" files to text/plain.
* Display improvements in the fossil bisect chart command.
* Updated the built-in SQLite to version 3.9.1 and activated JSON1 and
FTS5 support (both currently unused within Fossil).
Version 10.20 30-June-2015
--------------------------
1. Callouts with string arguments have been added.
2. Assertion code generator in JIT has been optimized.
3. The invalid pattern (?(?C) has a missing assertion condition at the end. The
pcre2_compile() function read past the end of the input before diagnosing an
error. This bug was discovered by the LLVM fuzzer.
4. Implemented pcre2_callout_enumerate().
5. Fix JIT compilation of conditional blocks whose assertion is converted to
(*FAIL). E.g: /(?(?!))/.
6. The pattern /(?(?!)^)/ caused references to random memory. This bug was
discovered by the LLVM fuzzer.
7. 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.
8. 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. This infelicity was discovered by the LLVM fuzzer.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. Negative relative recursive references such as (?-7) to non-existent
subpatterns were not being diagnosed and could lead to unpredictable behaviour.
This bug was discovered by the LLVM fuzzer.
15. The bug fixed in 14 was due to an integer variable that was unsigned when
it should have been signed. Some other "int" variables, having been checked,
have either been changed to uint32_t or commented as "must be signed".
16. 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.
17. The use of \K in a positive lookbehind assertion in a non-anchored pattern
(e.g. /(?<=\Ka)/) could make pcre2grep loop.
18. There was a similar problem to 17 in pcre2test for global matches, though
the code there did catch the loop.
19. 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.
20. 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.
21. Implemented PCRE2_NEVER_BACKSLASH_C.
22. The feature for string replication in pcre2test could read from freed
memory if the replication required a buffer to be extended, and it was not
working properly in 16-bit and 32-bit modes. This issue was discovered by a
fuzzer: see http://lcamtuf.coredump.cx/afl/.
23. Added the PCRE2_ALT_CIRCUMFLEX option.
24. Adjust the treatment of \8 and \9 to be the same as the current Perl
behaviour.
25. Static linking against the PCRE2 library using the pkg-config module was
failing on missing pthread symbols.
26. If a group that contained a recursive back reference also contained a
forward reference subroutine call followed by a non-forward-reference
subroutine call, for example /.((?2)(?R)\1)()/, pcre2_compile() failed to
compile correct code, leading to undefined behaviour or an internally detected
error. This bug was discovered by the LLVM fuzzer.
27. Quantification of certain items (e.g. atomic back references) could cause
incorrect code to be compiled when recursive forward references were involved.
For example, in this pattern: /(?1)()((((((\1++))\x85)+)|))/. This bug was
discovered by the LLVM fuzzer.
28. A repeated conditional group whose condition was a reference by name caused
a buffer overflow if there was more than one group with the given name. This
bug was discovered by the LLVM fuzzer.
29. A recursive back reference by name within a group that had the same name as
another group caused a buffer overflow. For example: /(?J)(?'d'(?'d'\g{d}))/.
This bug was discovered by the LLVM fuzzer.
30. A forward reference by name to a group whose number is the same as the
current group, for example in this pattern: /(?|(\k'Pm')|(?'Pm'))/, caused a
buffer overflow at compile time. This bug was discovered by the LLVM fuzzer.
31. Fix -fsanitize=undefined warnings for left shifts of 1 by 31 (it treats 1
as an int; fixed by writing it as 1u).
32. Fix pcre2grep compile when -std=c99 is used with gcc, though it still gives
a warning for "fileno" unless -std=gnu99 us used.
33. A lookbehind assertion within a set of mutually recursive subpatterns could
provoke a buffer overflow. This bug was discovered by the LLVM fuzzer.
34. Give an error for an empty subpattern name such as (?'').
35. Make pcre2test give an error if a pattern that follows #forbud_utf contains
\P, \p, or \X.
36. The way named subpatterns are handled has been refactored. There is now a
pre-pass over the regex which does nothing other than identify named
subpatterns and count the total captures. This means that information about
named patterns is known before the rest of the compile. In particular, it means
that forward references can be checked as they are encountered. Previously, the
code for handling forward references was contorted and led to several errors in
computing the memory requirements for some patterns, leading to buffer
overflows.
37. There was no check for integer overflow in subroutine calls such as (?123).
38. The table entry for \l in EBCDIC environments was incorrect, leading to its
being treated as a literal 'l' instead of causing an error.
39. If a non-capturing group containing a conditional group that could match
an empty string was repeated, it was not identified as matching an empty string
itself. For example: /^(?:(?(1)x|)+)+$()/.
40. In an EBCDIC environment, pcretest was mishandling the escape sequences
\a and \e in test subject lines.
41. In an EBCDIC environment, \a in a pattern was converted to the ASCII
instead of the EBCDIC value.
42. The handling of \c in an EBCDIC environment has been revised so that it is
now compatible with the specification in Perl's perlebcdic page.
43. Single character repetition in JIT has been improved. 20-30% speedup
was achieved on certain patterns.
44. The EBCDIC character 0x41 is a non-breaking space, equivalent to 0xa0 in
ASCII/Unicode. This has now been added to the list of characters that are
recognized as white space in EBCDIC.
45. When PCRE2 was compiled without Unicode support, the use of \p and \P gave
an error (correctly) when used outside a class, but did not give an error
within a class.
46. \h within a class was incorrectly compiled in EBCDIC environments.
47. JIT should return with error when the compiled pattern requires
more stack space than the maximum.
48. Fixed a memory leak in pcre2grep when a locale is set.
Version 6.5.2 - Dec 16 2015
[CHANGES]
New facilities:
o Improvements of gtags.conf
- Including from another file: Label syntax is expanded. (:tc=label[@file]:)
- Variable substitution: B shell like variable substitution is available.
- Addition of variables: 'bindir', 'datadir', 'libdir' and 'localstatedir'.
By default, these variables has a value given by the configure script.
- gtags.conf(5): Online manual of the configuration file.
o global: Now the -N(--nearness) option also works with the -P and -g command
as well as the tag search command.
o gtags.vim: New custom variable 'Gtags_Close_When_Single' (default 0).
If this variable is set to 1, quickfix window is closed when single tag.
Changed:
o gtags-cscope: Title changed to reduce misunderstanding.
Find locations calling this function: -> Find references of this function:
[FIXED BUGS]
o gtags.el: a strange error message in gtags-visit-rootdir was fixed.
$ cp /dev/null main.c
$ ls
main.c
$ emacs -f gtags-mode main.c
[Emacs mini buffer]
M-x gtags-visit-rootdir[ENTER]
Visit root directory: /tmp/test/[ENTER]
/tmp/test/main.c is not directory. <= STRANGE ERROR
o gtags (C, C++): Gtags couldn't handle enums in the case that there are
newlines between "enum" and " {". Now it can handle correctly.
+-------------
|typedef enum
|{
| E_FIRST = 1,
| E_SECOND
|} FIRST_SECOND;
+-------------
$ global -x '.*'
E_FIRST 3 test.h E_FIRST = 1,
FIRST_SECOND 5 test.h } FIRST_SECOND; <= E_SECOND not found
$ _
+-------------
|enum
|tag
|{ ... };
+-------------
$ global -x '.*'
$ _ <= tag not found
o gtags.conf: some part of a comment line (start with '#') was not skipped
when the line is very large. Now it is skipped correctly.
o gtags: If the DLL path includes ':', loading failed. Now it works.
Bugs Fixes
repowidget: fix handling of patch.extract() result (hg 3.6) (fixes#4390)
Improvements
doc: include link to download and use Python 2.7 SWIG bindings
2.9.0 (2015-12-15)
++++++++++++++++++
**Minor Improvements** (Backwards compatible)
- The ``verify`` keyword argument now supports being passed a path to a
directory of CA certificates, not just a single-file bundle.
- Warnings are now emitted when sending files opened in text mode.
- Added the 511 Network Authentication Required status code to the status code
registry.
**Bugfixes**
- For file-like objects that are not seeked to the very beginning, we now
send the content length for the number of bytes we will actually read, rather
than the total size of the file, allowing partial file uploads.
- When uploading file-like objects, if they are empty or have no obvious
content length we set ``Transfer-Encoding: chunked`` rather than
``Content-Length: 0``.
- We correctly receive the response in buffered mode when uploading chunked
bodies.
- We now handle being passed a query string as a bytestring on Python 3, by
decoding it as UTF-8.
- Sessions are now closed in all cases (exceptional and not) when using the
functional API rather than leaking and waiting for the garbage collector to
clean them up.
- Correctly handle digest auth headers with a malformed ``qop`` directive that
contains no token, by treating it the same as if no ``qop`` directive was
provided at all.
- Minor performance improvements when removing specific cookies by name.
0.5.1 -- 2015-12-16
-------------------
More information about this release can be found on the `0.5.1 milestone`_.
Fixed Bugs
~~~~~~~~~~
- Now papers over the differences in requests' ``super_len`` function from
versions prior to 2.9.0 and versions 2.9.0 and later.
----
19.2
----
* Pull Request #163: Add get_command_list method to Distribution.
* Pull Request #162: Add missing whitespace to multiline string
literals.
------
19.1.1
------
* Issue #476: Cast version to string (using default encoding)
to avoid creating Unicode types on Python 2 clients.
* Issue #477: In Powershell downloader, use explicit rendering
of strings, rather than rely on ``repr``, which can be
incorrect (especially on Python 2).
----
19.1
----
* Issue #215: The bootstrap script ``ez_setup.py`` now
automatically detects
the latest version of setuptools (using PyPI JSON API) rather
than hard-coding a particular value.
* Issue #475: Fix incorrect usage in _translate_metadata2.
----
19.0
----
* Issue #442: Use RawConfigParser for parsing .pypirc file.
Interpolated values are no longer honored in .pypirc files.
------
18.8.1
------
* Issue #440: Prevent infinite recursion when a SandboxViolation
or other UnpickleableException occurs in a sandbox context
with setuptools hidden. Fixes regression introduced in Setuptools
12.0.
v1.4.2
======
Nothing changed from v1.4.1.
v1.4.1
======
* Fix the compilation failure of cffi on CPython 3.5.0. (3.5.1 works;
some detail changed that makes some underscore-starting macros
disappear from view of extension modules, and I worked around it,
thinking it changed in all 3.5 versions---but no: it was only in
3.5.1.)
v1.4.0
======
* A `better way to do callbacks`__ has been added (faster and more
portable, and usually cleaner). It is a mechanism for the
out-of-line API mode that replaces the dynamic creation of callback
objects (i.e. C functions that invoke Python) with the static
declaration in ``cdef()`` of which callbacks are needed. This is
more C-like, in that you have to structure your code around the idea
that you get a fixed number of function pointers, instead of
creating them on-the-fly.
* ``ffi.compile()`` now takes an optional ``verbose`` argument. When
``True``, distutils prints the calls to the compiler.
* ``ffi.compile()`` used to fail if given ``sources`` with a path that
includes ``".."``. Fixed.
* ``ffi.init_once()`` added. See docs__.
* ``dir(lib)`` now works on libs returned by ``ffi.dlopen()`` too.
* Cleaned up and modernized the content of the ``demo`` subdirectory
in the sources (thanks matti!).
* ``ffi.new_handle()`` is now guaranteed to return unique ``void *``
values, even if called twice on the same object. Previously, in
that case, CPython would return two ``cdata`` objects with the same
``void *`` value. This change is useful to add and remove handles
from a global dict (or set) without worrying about duplicates.
It already used to work like that on PyPy.
*This change can break code that used to work on CPython by relying
on the object to be kept alive by other means than keeping the
result of ffi.new_handle() alive.* (The corresponding `warning in
the docs`__ of ``ffi.new_handle()`` has been here since v0.8!)
.. __: using.html#extern-python
.. __: using.html#initonce
.. __: using.html#ffi-new-handle
2015-12-15 meld 3.15.1
======================
Features:
* Text ignored by filters is now dimmed to give some visual feedback that
it's being ignored (David Rabel)
* Text filters now apply independently, improving consistency; note that
this is a behaviour change as filter order no longer matters, and filters
will always apply to the original (not the filtered) text (David Rabel,
Kai Willadsen)
* Recent menu items now show more detail in tooltips (Alan Suran)
* Update dialog action area layout for GTK+ theme changes (Kai Willadsen)
Fixes:
* Conflict resolution prompt now resolves properly again (Andrew Sutherland)
* Silence some GTK+ assertions on window close (Zain)
* Fix default filter issues from recent rework (Erik Schilling)
* Percent-containing commit messages no longer corrupt our recent commit
messages store (Kai Willadsen)
* Fix some problems with unicode user directories on Windows (Kai Willadsen)
* Fix encoding issues when saving files with load errors (Kai Willadsen)
* Fix drawing corruption when scrolling horizontally (Kai Willadsen)
* Fix clicking on the diffmap scrolling to the wrong location (Kai Willadsen)
* Fix off-by-one drawing error for final line in file (Kai Willadsen)
* Fix introspection requires to silence startup warnings (Kai Willadsen)
* Fix clearing syncpoints (Kai Willadsen)
* Add manual appdata kudos markers (Kai Willadsen)
* PEP8 fixes (David Rabel, Kai Willadsen)
Translations:
* Daniel Mustieles (es)
* Marek Černocký (cs)
* Milo Casagrande (it)
* Pedro Albuquerque (pt)
* Piotr Drąg (pl)
* Rafael Fontenelle (pt_BR)
--------------
Version 1.96b:
--------------
- Added -fpic to CFLAGS for the clang plugin, as suggested by Hanno Boeck.
- Made another clang change (IRBuilder) suggested by Jeff Trull.
- Fixed several typos, spotted by Jakub Wilk.
- Added support for AFL_SHUFFLE_QUEUE, based on discussions with
Christian Holler.
This library provides similar functionality to the builtin flag
library of go, but provides much more functionality and nicer
formatting. From the documentation:
Package flags provides an extensive command line option parser.
The flags package is similar in functionality to the go builtin
flag package but provides more options and uses reflection to
provide a convenient and succinct way of specifying command line
options.
New Libraries
VMD:
Variadic Macro Data library, from Edward Diener.
Updated Libraries
Atomic:
* Enforced proper alignment of atomic<> storage. This should fix possible issues on platforms that support atomic operations on data units larger than the native word size. This may also change binary layout of user's data structures that have atomic<> members.
* Fixed compilation for PowerPC with IBM XL C++ compiler. Corrected memory barriers in PowerPC assembler.
* Fixed compilation with MSVC-8 for ARM.
* Fixed compilation with gcc 4.4 for x86-64, when 128-bit atomic operations were used. (10994)
* Optimized some gcc assembler blocks for x86/x86-64 to reduce the number of used registers. This may require binutils 2.10 or later.
Chrono - 2.0.5:
Fixes:
* 10778 VC14 CTP4 Atomic don't compile with boost::chrono durations which are not TriviallyCopyable
* 10840 Missing std:: qualifier for puts call in test_7868.cpp
* 10851 Missing std:: qualifier for puts call in time_point_output.cpp
* 10893 Minor doc typo in Boost.Chrono
* 10992 Chrono IO state savers inconsistent with Boost.IO state savers
* 10995 duration_put::put_value truncates fractional part
* 11006 Impossible to instantiate time_fmt_io_saver due to several errors.
* 11012 chrono_io v2 fail to compile with boost::chrono::duration< boost::rational<int> >
Container:
* Implemented Polymorphic Memory Resources.
* Add more BOOST_ASSERT checks to test preconditions in some operations (like pop_back, pop_front, back, front, etc.)
* Added C++11 back/front operations to basic_string.
Fixed bugs:
* Trac 11627: "small_vector<T,n>::swap() appears to be broken".
* Trac 11628: "small_vector<int,n> iterates over elements in destructor".
* Trac 11697: "Wrong initialization order in tuple copy-constructor".
* Trac 11698: "Missing return statement in static_storage_allocator".
* GitHub 29: Doc fixes for flap_map complexity requirements.
* GitHub 31: DL_SIZE_IMPL also dereference addr.
Context:
* 11603 typo in PPC32/MACH-O asm
* support for CYGWIN
Core:
* In symbol demangling tools, added support for gabi++ ABI implementation used in Android NDK.
* Added a new enable_if_has_type tool for performing SFINAE checks for presence of a nested type.
more...
The packages this depends on all use mono and not mono2. While this
package may not build with later mono, it will *definitely* not build
with mixed mono versions.
