Thanks for all the suggestions! Given that the Perl module will, for now,
be more than just a web client (a portion of it will need to gather data by
parsing log files) I think I will go with App::Spoor - with the intent to
break off the part that has the webservice functionality into
> On Jan 23, 2019, at 9:16 AM, Rory McKinley wrote:
>
> I am developing a hosted application called Spoor. I would like to build a
> Perl client module for this application that will (amongst other things)
> interact with the Spoor Api.
>
> My current inclination is to call the module
There's APP:: - e.g. APP::Spoor::API & APP::Spoor::Client
On 23-Jan-19 10:16, Rory McKinley wrote:
> Hello
>
> I am developing a hosted application called Spoor. I would like to
> build a Perl client module for this application that will (amongst
> other things) interact with the Spoor Api.
>
>
Hello
I am developing a hosted application called Spoor. I would like to build a
Perl client module for this application that will (amongst other things)
interact with the Spoor Api.
My current inclination is to call the module Spoor::Client, but that will
mean that I will be creating a new
David Golden wrote:
Tim Bunce wrote:
On Fri, May 26, 2006 at 11:26:22PM +0200, David Landgren wrote:
Jeff Lavallee wrote:
of the SOAP::Lite details. Currently, I'm planning on calling it
Yahoo::Marketing. Yahoo::Marketing.pm itself would just serve as a
place holder (with POD) for the time
On Fri, May 26, 2006 at 11:26:22PM +0200, David Landgren wrote:
Jeff Lavallee wrote:
Hi all, before I upload a new module, I thought I'd make sure the
namespace I intend to use makes sense. I've been working on a set of
modules to make interacting with the next generation of Yahoo's
Tim Bunce wrote:
On Fri, May 26, 2006 at 11:26:22PM +0200, David Landgren wrote:
Jeff Lavallee wrote:
of the SOAP::Lite details. Currently, I'm planning on calling it
Yahoo::Marketing. Yahoo::Marketing.pm itself would just serve as a
place holder (with POD) for the time being, with all the
Hi all, before I upload a new module, I thought I'd make sure the
namespace I intend to use makes sense. I've been working on a set of
modules to make interacting with the next generation of Yahoo's
marketing web services easier. The modules insulate the user from a lot
of the SOAP::Lite
Jeff Lavallee wrote:
Hi all, before I upload a new module, I thought I'd make sure the
namespace I intend to use makes sense. I've been working on a set of
modules to make interacting with the next generation of Yahoo's
marketing web services easier. The modules insulate the user from a lot
of
On Tue, Feb 08, 2005 at 10:32:07AM +1300, Sam Vilain wrote:
Rocco Caputo wrote:
I think it would be misleading to imply that this code only works with
IRC.
Even so, what you are doing is inherantly an IRC-ish thing to want to do.
Wouldn't you still refer to non-IRC but IRC-like chatrooms
On Tue, Feb 08, 2005 at 10:32:07AM +1300, Sam Vilain wrote:
Rocco Caputo wrote:
I think it would be misleading to imply that this code only works with
IRC.
Even so, what you are doing is inherantly an IRC-ish thing to want to do.
Wouldn't you still refer to non-IRC but IRC-like chatrooms
On Sun, Feb 06, 2005 at 11:30:04PM -0600, David Nicol wrote:
there's an IRC top-level namespace, with IRC::Bot in it.
On Sun, 6 Feb 2005 17:56:01 -0500, Rocco Caputo [EMAIL PROTECTED] wrote:
I've written a module that threads chat messages, but I don't know
what to name it. Chat::Threader
there's an IRC top-level namespace, with IRC::Bot in it.
On Sun, 6 Feb 2005 17:56:01 -0500, Rocco Caputo [EMAIL PROTECTED] wrote:
I've written a module that threads chat messages, but I don't know
what to name it. Chat::Threader comes to mind.
http://cpan.org/modules/by-module/ doesn't list
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'
* 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
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
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::
Title: RE: Module naming advice
Which is my problem with 'alias.' Case-insensitive systems will
happily load a module with incorrect case (after loading,
though, using the name with incorrect case will cause problems).
Which module would get loaded?
Assuming they are both installed
On Jan 4, 2005, at 6:06 PM, Ovid wrote:
--- Eric Wilhelm [EMAIL PROTECTED] wrote:
Me too, except for how it reads in the 'use' statement.
use aka 'Really::Long::Module::Name';
Yeah, that bugs me too. Still, aka.pm is the name I lean toward.
It any case, it seems that
'alias.pm' might get
Hi all,
I'm about to release Aliased to the CPAN. Yeah, it's a root level
name, but it will soon become clear why it needs to be short.
SYNOPSIS:
use Aliased 'Really::Long::Module::Name';
use Aliased 'Really::Long::Conflicting::Module::Name' as MName;
use Aliased
On Tue, 4 Jan 2005 12:49:16 -0800 (PST), Ovid
[EMAIL PROTECTED] wrote:
I'm about to release Aliased to the CPAN.
[ . . . . ]
Basically, when you have long package names, it can be cumbersome to
retype the package name all the time. This module allows you to skip
that if the subroutines are
--- Kurt Starsinic [EMAIL PROTECTED] wrote:
On Tue, 4 Jan 2005 12:49:16 -0800 (PST), Ovid
[EMAIL PROTECTED] wrote:
I'm about to release Aliased to the CPAN.
[ . . . . ]
Basically, when you have long package names, it can be cumbersome
to
retype the package name all the time. This
My only quibble is that alias is 'less cumbersome' than aliased---sadly
already used...
--hsm
p.s. nice idea!!
-Original Message-
From: Ovid [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 04, 2005 1:49 PM
To: module-authors@perl.org
Subject: Module naming advice
Hi all,
I'm
On Tue, 2005-01-04 at 12:49 -0800, Ovid wrote:
Hi all,
I'm about to release Aliased to the CPAN. Yeah, it's a root level
name, but it will soon become clear why it needs to be short.
[...]
I've always felt that this one should have a lowercase name, since it's
rather pragma-ish. Are
On Jan 4, 2005, at 2:47 PM, Bruce J Keeler wrote:
I've always felt that this one should have a lowercase name, since it's
rather pragma-ish. Are pragmas allowed outside of the core Perl
distribution? Maybe it should be submitted as a core pragma, actually.
It's a really lightweight beast, and
aka is cool. I'll throw a few suggestions:
* mask
* camo
* pose
* cover
* veil
* guise
But yeah, aka is probly the best bet.
On Tue, Jan 04, 2005 at 02:55:08PM -0800, David Wheeler wrote:
On Jan 4, 2005, at 2:47 PM, Bruce J Keeler wrote:
I've always felt that this one should have a
David Wheeler wrote:
On Jan 4, 2005, at 2:47 PM, Bruce J Keeler wrote:
I've always felt that this one should have a lowercase name, since it's
rather pragma-ish. Are pragmas allowed outside of the core Perl
distribution? Maybe it should be submitted as a core pragma, actually.
It's a really
# The following was supposedly scribed by
# David Wheeler
# on Tuesday 04 January 2005 04:55 pm:
I agree that it should be lowercased; yes, there are modules on CPAN
that look like pragmas (such as only). I personally would prefer,
however, that the name tell me that it's doing something more
--- Eric Wilhelm [EMAIL PROTECTED] wrote:
Me too, except for how it reads in the 'use' statement.
use aka 'Really::Long::Module::Name';
Yeah, that bugs me too. Still, aka.pm is the name I lean toward.
It any case, it seems that
'alias.pm' might get confused with 'Alias.pm'.
Which is
On Tue, 2005-01-04 at 18:29 -0500, Randy W. Sims wrote:
There is Package::Alias[1]. Does the same thing, but I haven't used it.
Upon a quick glance, this does a similar thing but via a different
mechanism.
Ovid's module installs a constant sub into the caller's namespace which
returns the
From: Ovid [EMAIL PROTECTED]
--- Eric Wilhelm [EMAIL PROTECTED] wrote:
Me too, except for how it reads in the 'use' statement.
use aka 'Really::Long::Module::Name';
Yeah, that bugs me too. Still, aka.pm is the name I lean toward.
Agreed.
As for the interface, I really like the
David Wheeler wrote:
I agree that it should be lowercased; yes, there are modules on CPAN
that look like pragmas (such as only). I personally would prefer,
however, that the name tell me that it's doing something more than
loading a class; class and module don't do that.
However, this code
--- Sam Vilain [EMAIL PROTECTED] wrote:
However, this code reads very well:
use module 'Foo::Bar' as 'Bar';
use package 'Foo::Bar' as 'Bar';
'package' is a reserved word, so I won't use that. 'module' is worse
than 'class' because 'class' at least let's us know that this pragma is
only
# The following was supposedly scribed by
# Jenda Krynicky
# on Tuesday 04 January 2005 06:28 pm:
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);
Right. No, it's not even possible to
Ovid [EMAIL PROTECTED] writes:
[...]
That fails because it makes the common case more difficult:
use aliasing Really::Long::Class:Name;
# or
use aliasing Really::Long::Class:Name, as = CName;
However, I do like the name aliasing.pm Anyone else? It's not
perfect, but the one that
Thanks to everyone for their input. There was quite a bit more
discussion than I expected and most who have commented about the module
seem rather jazzed by the idea.
While the alternate implementation ideas sound interesting, I see no
compelling reason to change the interface. In large part
36 matches
Mail list logo
