On 7 Dec 2007, at 23:31, Andy Lester wrote:
[snip]
mantra
CPAN thrives because of the unfettered uploading of shit, not in
spite of it.
/mantra
[snip]
++ ** Inf
Adrian
On Sat, Dec 08, 2007 at 06:38:50PM +0100, Sébastien Aperghis-Tramoni wrote:
Tim Bunce wrote:
If there's a libfoo.so and I want to create a perl module/distribution
that's just a very thin wrapper around libfoo, what should I call it?
LibFoo
Lib::Foo
Lib::foo
Lib::libfoo
Tim Bunce wrote:
I was thinking in terms of a low-level 'thin' extension called
Lib::libmemcached with separate pure-perl modules implementing the Cache
and Cache::Cache interfaces.
Surely you found out about Cache::Memcached and friends? Basically what
you're proposing is a refactoring of
[[ This message was both posted and mailed: see
the To, Cc, and Newsgroups headers for details. ]]
In article [EMAIL PROTECTED], Tim Bunce
[EMAIL PROTECTED] wrote:
It's clear the Category::Foo scheme has the greater number of distributions.
It's also clear there's no firmly established best
On Mon, 2007-12-10 at 12:14 -0600, brian d foy wrote:
I'd prefer Lib:: to Cache::. As you say, Cache is a mess.
+1 Lib::Foo
-1 Lib::libfoo
--
--gh
On Dec 10, 2007 5:17 AM, Dominique Quatravaux [EMAIL PROTECTED] wrote:
+1, imho it makes good sense to have (some future version of)
Cache::Memcached depend on Lib::Memcached.
me too
Tim Bunce wrote:
I'm looking to build a very thin wrapper around libmemcached
(http://tangent.org/552/libmemcached.html)
a high-performance feature-rich interface to memcached.
[...]
I was thinking in terms of a low-level 'thin' extension called
Lib::libmemcached with separate pure-perl
On Mon, Dec 10, 2007 at 12:17:16PM +0100, Dominique Quatravaux wrote:
Tim Bunce wrote:
I was thinking in terms of a low-level 'thin' extension called
Lib::libmemcached with separate pure-perl modules implementing the Cache
and Cache::Cache interfaces.
Surely you found out about
On Mon, Dec 10, 2007 at 09:00:57PM +0100, Andreas J. Koenig wrote:
On Mon, 10 Dec 2007 11:07:38 +, Tim Bunce [EMAIL PROTECTED] said:
I'm looking to build a very thin wrapper around libmemcached
(http://tangent.org/552/libmemcached.html)
a high-performance feature-rich interface
Tim Bunce writes:
Re the choice of name for the low level library...
Lib::Memcached
Lib::memcached
Lib::libmemcached
My preference is for Lib::libmemcached because it emphasises the name
of the library that it's a wrapper for. (Think of libmemcached as a
brand name. easily
On Mon, 10 Dec 2007 11:07:38 +, Tim Bunce [EMAIL PROTECTED] said:
I'm looking to build a very thin wrapper around libmemcached
(http://tangent.org/552/libmemcached.html)
a high-performance feature-rich interface to memcached.
But there is BRADFITZ/Cache-Memcached-1.24.tar.gz
Tim Bunce wrote:
On Sat, Dec 08, 2007 at 06:38:50PM +0100, Sébastien Aperghis-Tramoni wrote:
Tim Bunce wrote:
If there's a libfoo.so and I want to create a perl module/distribution
that's just a very thin wrapper around libfoo, what should I call it?
LibFoo
Lib::Foo
12 matches
Mail list logo
