This release is largely a bug-fix release, but it does contain a couple of
small new features (next-unread-mailbox, $message_cache_clean).
The "change_folder_next" patches are gone, since a similar feature was added,
and it is now possible to use
bind index , next-unread-mailbox
to use , to cycle mailboxes with new mail
This module a simple file-based database. This database simply contains IP
blocks as keys, and countries as values. The data contains all public IP
addresses and should be more complete and accurate than reverse complete
COMPLETE and accurate than reverse DNS lookups.
This module can be used to automatically select the geographically closest
mirror, or to analyze your web server logs to determine the countries of
your visitors.
Rose::DB::Object is a base class for objects that encapsulate a
single row in a database table. It provides the following functions:
* Create a row in the database by saving a newly constructed object.
* Initialize an object by loading a row from the database.
* Update a row by saving a modified object back to the database.
* Delete a row from the database.
* Fetch an object referred to by a foreign key in the current object.
(i.e., "one to one" and "many to one" relationships.)
* Fetch multiple objects that refer to the current object, either directly
through foreign keys or indirectly through a mapping table. (i.e., "one
to many" and "many to many" relationships.)
* Load an object along with "foreign objects" that are related through any
of the supported relationship types.
Rose::DB is a wrapper and abstraction layer for DBI-related
functionality. A Rose::DB object "has a" DBI object; it is not a
subclass of DBI.
Tip: Are you looking for an object-relational mapper (ORM)? If so,
please see the Rose::DB::Object module. Rose::DB::Object is an ORM
that uses this module to manage its database connections. Rose::DB
alone is simply a data source abstraction layer; it is not an ORM.
Rose::DB is a wrapper and abstraction layer for DBI-related
functionality. A Rose::DB object "has a" DBI object; it is not a
subclass of DBI.
Tip: Are you looking for an object-relational mapper (ORM)? If so,
please see the Rose::DB::Object module. Rose::DB::Object is an ORM
that uses this module to manage its database connections. Rose::DB
alone is simply a data source abstraction layer; it is not an ORM.
Rose::Class is a generic base class for classes. It provides a
single class method (error), but may be expanded further in the
future.
A class that inherits from Rose::Class is not expected to allow
objects of that class to be instantiated, since the namespace for
class and object methods is shared. For example, it is common for
Rose::Object-derived classes to have error methods, but this would
conflict with the Rose::Class method of the same name.
The Rose::DateTime::* modules provide a few convenience functions
and objects for use with DateTime dates.
Rose::DateTime::Util contains a simple date parser and a slightly
customized date formatter.
Rose::DateTime::Parser encapsulates a date parser with an associated
default time zone.
This module (Rose::DateTime) exists mostly to provide a version
number for CPAN. See the individual modules for some actual
documentation.
This module provides a general-purpose clone function to make deep
copies of Perl data structures. It calls itself recursively to copy
nested hash, array, scalar and reference types, including tied
variables and objects.
The clone() function takes a scalar argument to copy. To duplicate
arrays or hashes, pass them in by reference:
The clone() function also accepts an optional second parameter that
can be used to limit the depth of the copy. If you pass a limit of
0, clone will return the same value you supplied; for a limit of
1, a shallow copy is constructed; for a limit of 2, two layers of
copying are done, and so on.
This module provides a general-purpose clone function to make deep
copies of Perl data structures. It calls itself recursively to copy
nested hash, array, scalar and reference types, including tied
variables and objects.
The clone() function takes a scalar argument to copy. To duplicate
arrays or hashes, pass them in by reference:
The clone() function also accepts an optional second parameter that
can be used to limit the depth of the copy. If you pass a limit of
0, clone will return the same value you supplied; for a limit of
1, a shallow copy is constructed; for a limit of 2, two layers of
copying are done, and so on.
* Decoration options interpreted under Windows-XP and UNIX as follows:
DECOR_SHRINKABLE means window may be smaller, but not larger, than
default size; DECOR_STRETCHABLE means window may be larger, but not
smaller, than default size; and finally, DECOR_RESIZE means window may
be both smaller or larger than default size.
* Fixed regression in glUseFXFont() when using Xft instead of XLFD.
* Fixed bug in FXVisual which caused drawing to FXBitmap to fail.
* Fixed bug FXWindow setDNDData() which affected MS-Windows clipboard operations.
* Fixed issue with bold-face text not drawing correctly in FXText if gap
happens to be in the text-fragment being drawn.
* Fixed issue in multi-head API access under older Windows operating
systems than Windows-XP.
* FXMDIChild resize animation speed changed a little bit.
* Some MacOS-X porting issues fixed.
This module provides a simple routine for installing code into
packages without looking at typeglobs or thinking about warnings
or strictures.
It also doesn't muddy up UNIVERSAL.
This module provides a simple routine for installing code into
packages without looking at typeglobs or thinking about warnings
or strictures.
It also doesn't muddy up UNIVERSAL.
This module understands the formats used by MySQL for its DATE,
DATETIME, TIME, and TIMESTAMP data types. It can be used to parse
these formats in order to create DateTime objects, and it can take
a DateTime object and produce a string representing it in the MySQL
format.
This module understands the formats used by PostgreSQL for its
DATE, TIME, TIMESTAMP, and INTERVAL data types. It can be used to
parse these formats in order to create DateTime or DateTime::Duration
objects, and it can take a DateTime or DateTime::Duration object
and produce a string representing it in a format accepted by
PostgreSQL.
A Time::Clock object is a twenty-four hour clock with nanosecond
precision and wrap-around. It is a clock only; it has absolutely
no concept of dates. Vagaries of date/time such as leap seconds
and daylight savings time are unsupported.
When a Time::Clock object hits 23:59:59.999999999 and at least one
more nanosecond is added, it will wrap around to 00:00:00.000000000.
This works in reverse when time is subtracted.
Time::Clock objects automatically stringify to a user-definable
format.
A Time::Clock object is a twenty-four hour clock with nanosecond
precision and wrap-around. It is a clock only; it has absolutely
no concept of dates. Vagaries of date/time such as leap seconds
and daylight savings time are unsupported.
When a Time::Clock object hits 23:59:59.999999999 and at least one
more nanosecond is added, it will wrap around to 00:00:00.000000000.
This works in reverse when time is subtracted.
Time::Clock objects automatically stringify to a user-definable
format.
< o p5-Business-ISBN-1.84
< o p5-Business-ISBN-Data-1.13
< o p5-MLDBM-Sync-0.30
< o p5-Mac-Macbinary-0.06
< o p5-Perl-Tidy-20070508
< o p5-Pod-Simple-3.05
< o p5-Spreadsheet-WriteExcel-2.18
< o p5-version-0.71
done.
Patch provided by Mark E. Perkins in PR 36465.
2007-03-03 Allison Randal <allison@perl.org>
* Release 3.05
Standardized all test files on 8.3 naming scheme for Perl core.
Applied test patches from Jerry Hedden for Perl core when
Encode not installed.
Applied test patch from Ken Williams for 5.005_04 compatibility.
Applied a patch from Christopher Madsen to fix architecture
directory searches on Gentoo.
Fixed a failing search test on Debian-based distributions caused
by Debian stripping Pod documentation out of core modules.
(Three cheers to the CPAN testers and James Ponza for sending
enough reports that I could work out the pattern.)
Patch provided by Mark E. Perkins in PR 36465.
0.06 - Fixed warning using IO::Scalar
(Thanks to Volker Moell)
0.05 * Fixed bug in extracting resource fork
(Thanks to Jorg Eschke <joerg@eschke.net>)
Patch provided by Mark E. Perkins in PR 36465.
1.84 - Tue Jan 9 23:10:00 2007
* updated copyright and license info
* no code changes, so no need to upgrade
Patch provided by Mark E. Perkins in PR 36465.
1.14 - Fri May 18 11:27:36 2007
* *Added 7000-8499 range from Greece (960) to fix RT #27107
1.13 - Tue Jan 9 23:12:56 2007
* updated copyright and license info
* no code changes, so no need to upgrade
1.12 - Tue Jan 9 23:11:33 2007
* updated copyright and license info
* no code changes, so no need to upgrade:
Patch provided by Mark E. Perkins in PR 36465.
2.18 January 18 2007 - Minor
! Correct invalid user set_column() calls to prevent
crashes after Excel patch KB918419 is applied.
Thanks to Sharron McKenzie for debugging.
! Fixed bug when writing comments longer than 8219 bytes.
Reported by jscaglione.
! Fixed bug when using copy() with merged formats.
Reported by jscaglione.
! Fixed bug where $@ was clobbered during garbage collection.
Reported by afoxson.
http://rt.cpan.org/Public/Bug/Display.html?id=24218
! Removed all non-ascii characters from main docs to
avoid problems with troff and man.
Reported by Ken Williams.
http://rt.cpan.org/Public/Bug/Display.html?id=20948
+ Added autoloading of OLE::Storage_Lite, when available,
to create workbooks larger than 7MB. It is no longer
required to explicitly use ::Big.
+ Added handling of Unicode sheet names in formulas
as suggested by Zhur:
http://rt.cpan.org/Public/Bug/Display.html?id=20059
Based on patch provided by Mark E. Perkins in PR 36465.
0.32 2007.05.05
- Remove the memory_leak test as well as it still fails.
0.31 2007.05.03
- Require IO::Scalar always as OLE::Storage_Lite needs it but does not prereq it
- disable some of the tests that don't yet work on 64 bit due to number precision
in order to allow automatic installation
0.30 2007.03.31
- add some more tests
- add test to see memory leak using Proc::ProcessTable
- Start using Scalar::Util qw(weaken) to (hopefully) avoid memory leak
- It seems we did not check correctly if PERLIO is available in Makefile.PL
now it is the same test we do in the code itself.
- Flag1904 renamed to Flg1904 in documentation (Chad) RT #24293
0.29 2007.03.30
- clean up basic.t to skip tests that need additional and missing module
- No more need for IO::Scalar if PERLIO is available (H.Merijn Brand)
0.28 Wed Jan 7, 2007
- Documentation update
- Add t/parse.t
- Add sample/parse.pl
- fix some syntax errors in the sub-modules
0.27 Wed Jan 3, 2007
- See changes in the 0.27_XX versions
0.27_03 Thu Nov 2, 2006
- Officially receive maintainership (Gabor Szabo)
- slight code cleanup
- more sample test
0.27_02
- Fixing another warning:
Character in 'c' format wrapped in pack
http://rt.cpan.org/Ticket/Display.html?id=18063
(Grant Stevens)
- More test, enable use of Devel::Cover
0.27_01 Mon Sep 11, 2006
- Moving test.pl to t/ and using Test::More
- Add tests running (some of the) sample files
- Add 'use warnings', remove prototypes
- Fix the warning in Spreadsheet::ParseExcel::FmtDefault
Character in "C" format wrapped at .../Spreadsheet/ParseExcel/FmtDefault.pm line 68.
http://rt.cpan.org/Public/Bug/Display.html?id=7376
(Slaven ReziÄ?and others)
Patch provided by Mark E. Perkins in PR 36465.
2007-04-17 John Peacock <jpeacock@cpan.org>
Neglected to delete or comment out a $DB::single (again).
2007-04-17 John Peacock <jpeacock@cpan.org>
One last place that needed a leading 'v' (for non-magic v-strings).
2007-04-17 John Peacock <jpeacock@cpan.org>
v-string created version objects always stringify with a leading 'v' for
consistency's sake, since we have no way of knowing whether one was present
for 5.6.0 <= Perl < 5.8.1 (non-magic v-strings).
2007-04-17 John Peacock <jpeacock@cpan.org>
When copying an existing version object, forgot to copy the original string
representation.
2007-04-14 John Peacock <jpeacock@cpan.org>
Return original string value for all stringification cases except for
qv(1.2) which returns 'v1.2' for roundtrip purposes.
2007-04-12 John Peacock <jpeacock@cpan.org>
Output the original string form for numeric versions for XS code now.
Ready to release to CPAN.
2007-04-12 John Peacock <jpeacock@cpan.org>
It will be less surprising to overload string comparisons (now that the
default stringification is identical to the initializer) than it would be
to not overload them.
2007-04-11 John Peacock <jpeacock@cpan.org>
Better way to handle the undef initialization case.
2007-04-11 John Peacock <jpeacock@cpan.org>
Disallow string comparisons with version objects. Tests adjusted to use
numeric comparisons only.
2007-04-11 John Peacock <jpeacock@cpan.org>
Cache the original string used to initialize the version object and return
that when stringifying. Only works with pure Perl class for the moment.
2007-03-18 John Peacock <jpeacock@cpan.org>
Add more text to README on v-string support.
2007-03-18 John Peacock <jpeacock@cpan.org>
Now supports non-magical v-strings (Perl 5.6.0-5.8.0)!
Polymorphic error messages from 5.6.0 onwards.
2007-03-10 John Peacock <jpeacock@cpan.org>
Polymorphic error messages work everywhere except XS under 5.6.2. :(
2007-03-10 John Peacock <jpeacock@cpan.org>
Polymorphic error messages now working (and tested) in pure Perl module.
2007-02-13 John Peacock <jpeacock@cpan.org>
Don't need to explicitely specify the MAN3POD stuff, since EU::MM will now
do that automatically (since the POD is mentioned in PM).
Actually, magic v-strings came in at 5.8.1, not 5.8.0 (spotted in the
bleadperl variant).
