+ Added compiler directives for C++.
+ Improved the method "Norm()".
+ Removed "Carp::Clan" from the distribution (available separately).
+ Added "Bit::Vector::String" for generic string import/export functions.
+ Added a new test file "t/40__auxiliary.t" for "Bit::Vector::String".
+ Fixed a bug in method "Copy()" concerning sign (MSB) extension.
various other things with a patch. It basically allows you to create a chain of
readers that can read a patch, remove files from a patch, add CVS context, fix
up the patch root according to CVS, and output the patch as raw unified or
through a template processor (used in some places to output a patch as HTML).
# 1.2.0
* New algorithm added: Bidirectional Dijkstra's shortest path
* A lot of bugfixes
* Revised documentation
# 1.1.0
* Returned to the libtool versioning style
* New algorithms added
o Dijkstra's shortest path
o Bellman Ford shortest path
o New variant of Maximal Flow
* graph::load now creates nodes in the same order as they are in the gml file
* graph::load now with parameter 'preserve_ids' to use the same ids as in the gml file
* A lot of bugfixes
* Documentation adapted to doxygen
# 1.0.0
* First stable release
* quick fix of bug in graph::del_node (thanks to David Auber)
* bug fix in graph::hide_node (thanks to David Auber)
* optimization of reallocation procedure in node_ and edge_maps (again, thanks to David)
math/cassowary and I'll update gtl in a minute.
DESCR:
GTL is a graph library based on STL. For the design of GTL's API the
API of LEDA has served as a basis. GTL contains the classes needed to
work with graphs, nodes and edges and some basic algorithms (DFS, BFS,
topsort ...) as building blocks for more complex graph algorithms.
This package contains an older version of the library, for a newer
version use the gtl package.
quotearg_buffer_restyled(). Google suggests this function has issues
with other non-gcc compilers using optimisation as well.
Notable fixes include net/libIDL's parser.y
Bugs fixed in 1.9.3:
* Bug introduced by 1.9:
- Dependency tracking using mode "dashmstdout" or "dashXmstdout" did
not work for libtool objects compiled with --tag (i.e., compiled
with Libtool 1.5 or later). The compilation would succeed, but
`depcomp' would emit a warning and not output any dependency
information.
* Long standing bugs:
- Ignore comments from augmented variables, so that
FOO = foo # bar
FOO += baz
no longer results in `FOO = foo # bar baz'.
- `install-sh -d a/b/' failed to create `a/b/' because of the trailing `/'.
- _PROGRAMS now always create programs. Before 1.9 it would
mistakenly create a libtool library if the name of the program
ended in `.la'. Between 1.9 and 1.9.2 a program with such a name
would fail to build because half the code was assuming a program
was being built, while the other half was considering a library...
- `compile' now handles `*.obj' objects.
- `aclocal' recognizes AC_DEFUN_ONCE.
* Noteworthy manual updates:
- LIBOBJS: more documentation and an example setup.
- Libtool Convenience Libraries: show how to force the linker selection.
- Extending: more comments about install-data-hook vs install-exec-hook.
- Clean: document -local targets.
the header file <rfuncs.h> through a compiler flag along with some
unnecessary linker flags. This should hopefully resolve pkg/27631,
security/gpgme dies on configure.
From ChangesLog:
* Improve robustness. (client/server)
Make this more friendly to userlevel POSIX thread libraries.
* Improve performance to parse rcsfile(5) based files.
* When -u/-g is specified, drop the privilege. (server)
* Update scanfiles when changes anything only.
Changes:
- UTF-8 filenames, while still not handled correctly, are handled a little
more gracefully. That is to say, the library doesn't fail to open files
with filenames using characters outside the ASCII subset. I'm very
interested in any information as to the "right" way to handle filenames
of this sort.
- Files not containing a compressed section are handled properly, such as
.chw files. These files seem to contain information about compression,
but the information is invalid or empty. The library deals gracefully
with this now.
- Files compressed with different options were not being decompressed
properly. In particular, if the "reset interval" for the compressed
section was other than 2 block sizes, it could fail to read some of the
files.
- The caching system was improved slightly, in conjunction with this
previous bugfix.
PKGREVISIONs of packages including it, because the recent update of
libexif changed the major version number of libexif. Noted by dieter
and Jeremy C. Reed on tech-pkg@.
Fixes
- If the toplevel directory of a source isn't writable, then mark the
whole source as readonly (Mark)
- Plug various leaks (Kjartan)
Translators
- Christophe Merlet (RedFox) (fr)
- Alessio Frusciante (it)
- Žygimantas Beručka (lt)
- Li-Jen Hsin (zh_TW)
* configure.in (VERSION): Bump to 1.4.2.
* NEWS: Describe 1.4.2's changes.
* src/m4.c (reference_error): Preserve errno, since M4ERROR
relies on this.
* src/builtin.c (m4_esyscmd): Clear errno before calling popen.
(m4_maketemp): Clear errno before calling mkstemp.
* src/path.c (path_search): Don't let "free" trash errno when
returning NULL.
* src/output.c (insert_file): Don't assume errno has a valid
value simply because fread returns zero. This fixes a
portability bug reported by Marion Hakanson in
<http://lists.gnu.org/archive/html/bug-m4/2004-07/msg00029.html>.
Fixes PR pkg/27301.
IO::Util - A selection of general-utility IO function
This is a micro-weight module that exports just a couple of
functions of general utility in IO operations.
OOTools is a collection of pragmas to easily create constructors methods and
lvalue accessor methods at compile time. OOTools distribution includes:
Class::constr Pragma to implement constructor methods
Class::props Pragma to implement lvalue accessors with options
Class::group Pragma to implement group of properties accessors with options
Object::props Pragma to implement lvalue accessors with options
Object::group Pragma to implement group of properties accessors with options
strerror_r(). These are thread safe versions of the corresponding functions
without the "_r". The package is implemented so that it may be used simply
by including it's buildlink3.mk file.
This is a simple module that factory classes can use to generate new
types of objects on the fly, providing a consistent interface to common
groups of objects.
Factory classes are used when you have different implementations for the
same set of tasks but may not know in advance what implementations you
will be using.