ok benoit@
This Perl module contains common or near-common code factored out of
Date::Tolkien::Shire and DateTime::Fiction::JRRTolkien::Shire. This is
mostly data and calculations common to the two modules, but there is
also a piece of new functionality: an output formatter for Shire dates
analogous to strftime(). All functionality is provided by subroutines.
Because of its nature, you probably do not want to use this module
directly. At least, not without looking into Date::Tolkien::Shire which
is a semi-thin object-oriented front end to this module, or
DateTime::Fiction::JRRTolkien::Shire which is a somewhat-quirky member
of the DateTime family.
- don't use a 2 bits bool field (makes no sense, clang errors out)
- switch a function from __inline to __inline static, like the other
function in this header
since SHARED_ONLY support was removed across the ports tree the perl module
no longer adds it, so it must be done manually for any perl ports that
provide perl shared-library modules (i.e. libdata/perl5/site_perl/$ARCH/*.so)
and you must not remove them from WANTLIB even if they show as "Extra".
LAStools: tools for efficient point-cloud processing
* laszip compresses the LAS files in a completely lossless manner
* lasinfo prints out a quick overview of the contents of a LAS file
* lasindex creates a spatial index LAX file for fast spatial queries
* las2las extracts last returns, clips, subsamples, translates, etc ...
* lasmerge merges several LAS or LAZ files into a single LAS or LAZ file
* txt2las converts LIDAR data from ASCII text to binary LAS format
* las2txt turns LAS into human-readable and easy-to-parse ASCII
* lasprecision analyses the actual precision of the LIDAR points
ok zhuk@
tests of p5-Net-IDN-Encode crashed the Perl process. There was no
proper protection against heap overflow in the XS part. Grow the
destination string in encode_punycode() and decode_punycode() before
writing to it. This has to be checked every time.
Take maintainer.
OK jca@
