Re: Including a 480K data file with a module

2005-01-06 Thread Ken Williams
On Jan 6, 2005, at 12:12 AM, Scott W Gifford wrote: Ken Williams [EMAIL PROTECTED] writes: On Jan 5, 2005, at 3:29 PM, Graciliano M. P. wrote: You should compress the data and than append it with __DATA__ or as a string saved with Base64 to avoid binary errors. I think not - then you'd have to

Re: Including a 480K data file with a module

2005-01-06 Thread _brian_d_foy
In article [EMAIL PROTECTED], Scott W Gifford [EMAIL PROTECTED] wrote: Why not just leave it uncompressed, and let the compression of the whole package into Geo-PostalCode-US-0.1.tar.gz take care of compressing it? I recommend not doing that. I had a lot of problems distributing the data

When the prophet won't go to the mountain, the mountain must go to the prophet.

2005-01-06 Thread A. Pagaltzis
Oh look, it's an Atom newsfeed for cpanratings.perl.org: http://plasmasturm.org/feeds/cpanratings/ The scraper is available from http://plasmasturm.org/feeds/ in case anyone is curious. The script is generated by scraping the CPAN ratings front page every six hours, so please don't refresh

Re: Including a 480K data file with a module

2005-01-06 Thread Scott W Gifford
_brian_d_foy [EMAIL PROTECTED] writes: In article [EMAIL PROTECTED], Scott W Gifford [EMAIL PROTECTED] wrote: Why not just leave it uncompressed, and let the compression of the whole package into Geo-PostalCode-US-0.1.tar.gz take care of compressing it? I recommend not doing that. I had

Re: Including a 480K data file with a module

2005-01-06 Thread Scott W Gifford
Chris Josephes [EMAIL PROTECTED] writes: [...] 2. Include a make install-data target that will unzip the data, and then install it in a standard location your module will search by default. Would /usr/share/postal/us be a bad place? Is anyone else doing this? The problem is that you can't

Re: Module naming advice

2005-01-06 Thread Alberto Manuel Brandao Simoes
A. Pagaltzis wrote: * Jenda Krynicky [EMAIL PROTECTED] [2005-01-05 01:28]: Has anyone ever seen a module with a space in the name? If not we might just as well use use aka 'Really::Long::Module::Name as MName' qw(foo bar baz); How about this? use aka [ 'Really::Long::Module::Name' = 'Name'

Re: Class::Validation

2005-01-06 Thread A. Pagaltzis
* Daisuke Maki [EMAIL PROTECTED] [2004-11-23 04:06]: In fact, it's really a role-type class, and something like Class::Validating might be better. On top of Dave's suggestion I'm thinking towards the line of Class::ValidateArgs, Class::Validation, Class::ParamValidation, etc. I like

Re: Module Name: Net::Lite::FTP

2005-01-06 Thread A. Pagaltzis
* Dariush Pietrzak [EMAIL PROTECTED] [2005-01-05 11:59]: This module is very simple, but provides access to TLS-enabled servers, and is going to be a testbed for few relatively new extensions to ftp Intented usage: my $tlsftp=Net::Lite::FTP-new(); Bad name. That should be

Re: Module naming advice

2005-01-06 Thread A. Pagaltzis
* Alberto Manuel Brandao Simoes [EMAIL PROTECTED] [2005-01-06 21:19]: My 5 words... use aka Name Really::Lond::Module::Name qw(foo bar baz) Except that's not valid syntax, and the version which would be has already been discussed and dismissed. Regards, -- #Aristotle *AUTOLOAD=*_;sub

Re: Including a 480K data file with a module

2005-01-06 Thread Chris Josephes
On Thu, 6 Jan 2005, Scott W Gifford wrote: If the user has custom data, they would just install Geo::PostalCode and build their own database (it includes a short script to do this, and the process takes about 2 minutes). Geo::PostalCode::US doesn't replace Geo::PostalCode, but just adds a

Re: Including a 480K data file with a module

2005-01-06 Thread Chris Josephes
On Thu, 6 Jan 2005, Chris Josephes wrote: 2. Include a make install-data target that will unzip the data, and then install it in a standard location your module will search by default. Would /usr/share/postal/us be a bad place? Is anyone else doing this? As a quick follow-up to my own post,

Re: When the prophet won't go to the mountain, the mountain must go to the prophet.

2005-01-06 Thread David Landgren
A. Pagaltzis wrote: Oh look, it's an Atom newsfeed for cpanratings.perl.org: Man, when I read the subject I thought your email was going to be about penis enlargement. Excellent work. And you've got a feed for QDB. Marvellous. David

Re: Module naming advice

2005-01-06 Thread David Nicol
I don't understand what's being contemplated here. I think we're talking about recreating Package::Alias, which is essentially sugar around use really::long::name::ending::bar; BEGIN { *bar:: = \*really::long::name::ending::bar:: } after which the methods in RLNEB can be referred to with

Re: Module Name: Net::Lite::FTP

2005-01-06 Thread David Nicol
call it Net::FTP2 with the same caveats and reccommenddations and include blat and slurp methods! I don't want to have to create and release Net::FTP2::blat when I want to work with remote data over secure FTP. my two rusty bottlecaps, david nicol

Re: Module naming advice

2005-01-06 Thread Bruce J Keeler
On Thu, 2005-01-06 at 20:08 -0600, David Nicol wrote: I don't understand what's being contemplated here. I think we're talking about recreating Package::Alias, which is essentially sugar around use really::long::name::ending::bar; BEGIN { *bar:: = \*really::long::name::ending::bar::

I named it aliased.pm

2005-01-06 Thread Ovid
Since absolutely no one could agree on the name, I went ahead and uploaded the module as 'aliased'. Right now, 0.1 is available on the CPAN, but .11 is on its way. The code is the same, but I accidentally uploaded it before I had finished the docs. The interface is slightly different, too. #