the plugging of several memory leaks, fixes to the regular expression
engine, the addition of a Unicode character classes, better support for
64-bit platorms, and updates of many modules in the base Perl Library.
See perldelta.pod for more details.
Also update p5-Data-Dumper, p5-Devel-DProf, and p5-Devel-Peek to the
latest versions distributed with the perl-5.6.1 sources, and libperl to
5.6.1 to match the perl package.
- Don't use $, internally. Apparently this is usually undefined.
Instead, the convenience methods now simply take an array of messages
and turn it into a scalar by doing "@_".
- Allow ApacheLog to take either an Apache or Apache::Server object.
- Fix callback documentation in Log::Dispatch::Output.
- Add flush method to Log::Dispatch::Email.
Trio is a fully matured and stable set of printf and string functions designed
be used by applications with focus on portability or with the need for
additional features that are not supported by standard stdio implementation.
There are several cases where you may want to consider using trio:
1.Portability across heterogeneous platforms.
2.Embedded systems without stdio support.
3.Extendability of unsupported features.
4.Your native version don't do everything you need.
${BUILDLINK_INCDIR} and ${BUILDLINK_LIBDIR}, to be used by other packages.
* Use buildlink.mk files to get dependencies and to prevent unintended
linking against installed libraries or finding installed headers except
for those that are explicitly linked into ${BUILDLINK_INCDIR} and
${BUILDLINK_LIBDIR}.
${BUILDLINK_INCDIR} and ${BUILDLINK_LIBDIR}, to be used by other packages.
* Use buildlink.mk files to get dependencies and to prevent unintended
linking against installed libraries or finding installed headers except
for those that are explicitly linked into ${BUILDLINK_INCDIR} and
${BUILDLINK_LIBDIR}.
* Don't prototype history functions directly, but use
<readline/history.h> to pull them in. This allows us to use libedit's
readline emulation.
* Change from USE_PERL5 to a build dependency on perl -- it's only used to
generate a header file during the build.
${BUILDLINK_INCDIR} and ${BUILDLINK_LIBDIR}, to be used by other packages.
* Remove unnecessary include of bsd.prefs.mk.
* Change how we disable pthreaded version of lwp by passing values to the
configure script via the environment, instead of requiring an extra file.
provide a single front end for all tests. Beyond this, DejaGnu offers
several advantages for testing:
- The flexibility and consistency of the DejaGnu framework
make it easy to write tests for any program.
- DejaGnu provides a layer of abstraction which makes all
tests (if correctly written) portable to any host or target
where a program must be tested. For instance, a test for
GDB can run (from any Unix based host) on any target
architecture supported by DejaGnu. Currently DejaGnu runs
tests on several single board computers, whose operating
software ranges from just a boot monitor to a full-fledged,
Unix-like realtime OS.
- DejaGnu is written in expect, which in turn uses Tcl
(Tool command language). The framework comprises two parts:
the testing framework and the testsuites themselves. Tests
are usually written in expect using Tcl.
Added untested SEEK, TELL, and EOF methods to IO::Scalar and
IO::ScalarArray to support corresponding functions for tied
filehandles
Removed not-fully-blank lines from modules; these were causing lots
of POD-related warnings
IO::Scalar objects can now be made sensitive to $/ . Pains were
taken to keep the fast code fast while adding this feature
IO::Scalar has a new sysseek() method
This is NetBSD's make(1) utility, with a configure script and
supporting replacements for various NetBSD library routines, ported to
other Operating Systems by Simon Gerraty. Solaris, SunOS, HP-UX,
Linux and AIX are amongst the operating systems supported.
need updates of GNOME programs, most nobably evolution. With gal-0.7,
at least evolution-0.10 compiles. This addresses (part of) PR 13013 by
Matthias Scheler <tron@netbsd.org>.
Use BUILDLINK_INCDIR, BUILDLINK_LIBDIR for locations of linked headers
and libraries. Create a variable BUILDLINK_TARGETS whose value is the
list of build-link targets to execute.
The Params::Validate module provides a flexible system for validation
method/function call parameters. The validation can be as simple as
checking for the presence of required parameters or as complex as
validating object classes (via isa) or capabilities (via can),
checking parameter types, and using customized callbacks to ensure
data integrity.
- Bug fixes.
- Simplify the colour combo/palette/group relationship.
- Add instance code to colour groups.
- README: Added a line about contributed code license and such
here.
- New routines to create an option menu of character sets.
- Remove change signal and add new custom_color_add signal.
- Added e-sorter-array, e-util, e-categories-master-list-*
${PREFIX}/share/examples/cdecl. Also patch sources to rename instances
of setprogname() to mysetprogname(), as setprogname() is part of the
standard library in NetBSD>1.5.
