Mark Stosberg wrote:
> I think I want to make some slight tweaks to the API, but it's about
> ready for 1.0. It's built around my own common usage: Uploading images
> and storing meta data in a database. However, it works fine for non
> images as well.
I think this module should be called CGI::Im
Sam Vilain wrote:
> 11) String Processing, Language Text Processing, Parsing and Searching
> * Stemming algorithms
> * Natural Languages
> * Specific Natural Languages
+ * Templating modules
A
David Wheeler wrote:
> So, what do people like or prefer, and why? Is there a consensus on
> this? If so, what is it?
I manually give the main module in a distribution a "real" version number
such as 2.00, 2.01, and so on. Naturally this changes on every release.
All the other modules in a dis
Marco Marongiu wrote:
> NAME
> Date::Iterator - Iterate over a range of dates
Nice!
> $i = Date::Iterator->new( from => [2003,12,1], to => [2003,12,10] )
As a matter of convenience, can I suggest that in addition to list
references you also allow dates to be specified as strings?
Scott R. Godin wrote:
> judging by the results I get from http://validator.w3.org/ the XHTML Strict
> usage currently in Pod::Html is way premature.. the results are ugly to say
> the least,
You might find Pod::POM useful. It has a standard POD to HTML translator
built in, but the real feature
David Kaufman wrote:
> if you have any doubt that any sufficiently advanced template systems is
> indistinguishable from a programming language, take a closer look at ASP,
> PHP, and CFML.
I wouldn't call any of them either "sufficiently advanced" nor "template
systems". They are all programming
Terrence Brannon wrote:
> TT2 still has issues with numerical and string equivalence checks:
True. It was a difficult design decision - to keep the language simple,
but at the risk of making it too simple to be useful.
In version 3, the parser will be much more flexible. You'll be able
to conf
Chris Josephes wrote:
> 2. Text::MetaText
[...]
> ...but it has a very limited command set with no means
> to allow for expansion.
and has been superceded by the Template Toolkit.
A
On Tue, Jul 16, 2002 at 08:27:17PM -0500, Ade Olonoh wrote:
>Another problem would be the Namespace. MetaInfo sees available.
> I could release the modules as MetaInfo::Miner::- and
> MetaInfo::Store::-- if I wanted to release both sets.
How about something like Data::MetaDat
