Re: Module Naming & Relevancy

On 11/06/2022 09:21, Neil Bowers wrote: I’d go with WebService::PACER – WebService is *one* of the standard namespaces on CPAN for this sort of module :-) You could slip a USCourt in the middle, but I don’t think that’s necessary – better to keep things simple. It's not *necessary* but it i

Re: Module Naming & Relevancy

api) then qualification would be at the other end... WebService::PACER::USCourt (for example). But PACER could be a term that is eventually overloaded when someone else names their own unrelated Web service PACER. While only a slim possibility I don't think forwardly ensuring unambiguous module

Re: Module Naming & Relevancy

Is it specific to `UsCourt`? Could there be later a `MexicoCourt`? On Sat, Jun 11, 2022, 10:22 Neil Bowers wrote: > Hi Brian, > > I’d go with WebService::PACER – WebService is *one* of the standard > namespaces on CPAN for this sort of module :-) > > You could slip a USCourt in the middle, but I

Re: Module Naming & Relevancy

Hi Brian, I’d go with WebService::PACER – WebService is *one* of the standard namespaces on CPAN for this sort of module :-) You could slip a USCourt in the middle, but I don’t think that’s necessary –  better to keep things simple. Cheers, Neil

Re: Module Naming & Relevancy

On 6/9/22 21:02, Brian Erickson wrote: I am developing a module for interacting with the United States PACER (Public Access to Court Electronic Records) API. PACER is a US government service that provides access to over one billion documents relating to cases that were, or are being, tried befor

Module Naming & Relevancy

I am developing a module for interacting with the United States PACER (Public Access to Court Electronic Records) API. PACER is a US government service that provides access to over one billion documents relating to cases that were, or are being, tried before US district courts, US court of appeals

Re: Noob questions on module naming and repo organization

On 6/22/21 8:59 PM, Leam Hall wrote: If you assume I know nothing, you'll be pretty close to right.  :) I'm working on an application that collates text files into a "book". It will also provide grade level reports and alternate output formats. I'm looking for wisdom on how to organize the Per

Noob questions on module naming and repo organization

If you assume I know nothing, you'll be pretty close to right. :) I'm working on an application that collates text files into a "book". It will also provide grade level reports and alternate output formats. I'm looking for wisdom on how to organize the Perl code and how to set up the git repo

Re: Module naming advice, please.

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 Webservice::S

Re: Module naming advice, please.

> 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 Spoor::

Re: Module naming advice, please.

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.  > >

Module naming advice, please.

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 top-l

Re: Module naming - exposing Win API function ShellExecute

Hi Timothy, I just wanted to point out that there is some prior work in the realm of a thing or two you mentioned in other modules: Shell quoting: As you mentioned, it's a big deal. Haarg has done quite a bit of work to make this as complete as possible: https://metacpan.org/pod/Win32::ShellQuote

Module naming - exposing Win API function ShellExecute

Hello, For ::ShellExecute API function on Windows I got confused with the possible names like:  - Win32::ShellExecute  - Win32::API::ShellExecute  - Win32API::ShellExecute I noticed Win32API:: namespace mostly uses XS modules to expose the API, while my module uses dynamic loading of .dll fi

Re: Module Naming: a Path::Iter::Rule subclass which scans FTP sites

On Thu, May 4, 2017 at 12:53 PM, Reini Urban wrote: > Thinking about it, I like the name Net::FTP::Path::Iter best > > Reini Urban > rur...@cpan.org > That sounds good to me as well. Thanks!

Re: Module naming -- processing 3D JPEG files...

JPS file, and > likewise take an MPO or JPS file and split it out into two > separate JPEG files. That's what these modules will do. > > OK -- probably more than you wanted to know. > > As for the module names, stereographic images are commonly > referred to as 3D images, b

Re: Module Naming: a Path::Iter::Rule subclass which scans FTP sites

Thinking about it, I like the name Net::FTP::Path::Iter best Reini Urban rur...@cpan.org

Re: Module Naming: a Path::Iter::Rule subclass which scans FTP sites

Correction, it subclasses Path::Iterator:Rule, which makes the names even longer! On Thu, May 4, 2017 at 10:07 AM, Diab Jerius wrote: > Howdy, > > I've developed a module which subclasses Path::Iter::Rule and uses > Net::FTP to scan FTP sites [1]. I'm stuck on naming it. > > * Net::FTP::Rule (

Module Naming: a Path::Iter::Rule subclass which scans FTP sites

Howdy, I've developed a module which subclasses Path::Iter::Rule and uses Net::FTP to scan FTP sites [1]. I'm stuck on naming it. * Net::FTP::Rule (the current working name) is just plain opaque. * Path::Iter::Rule::FTP seems backwards. FTP should be up front. On the other hand, maybe PIR will

RE: Module naming -- processing 3D JPEG files...

Which would give you something like Image::TriD::StereoPairs::MPO I'm liking 'StereoPairs'. Unless there are strenuous objections, I plan to go with... Image::3D::StereoPair::MPO Now all I have to do is write the software. :-) Thanks to all for the feedback. ...BC -- ---

Re: Module naming -- processing 3D JPEG files...

> > Some would consider the following to be even more general and > thus better: > >Image::3D::Pairs::MPO >Image::3D::Pairs::JPS >Image::3D::Pairs::JPG > >Image::3D::Lenticular >Image::3D::VR >Image::3D::Holo >Image::3D::DepthMap > > But wouldn't this break the rule for

Re: Module naming -- processing 3D JPEG files...

I'm sure you'll find a suitable compromise. My concern is the future - ensuring that the next format and/or packaging of multiple images has a place to fit. These things tend to evolve (complete with survivors and dead-ends.) But Image::3D:: isn't the only way to express three-dimensional... th

RE: Module naming -- processing 3D JPEG files...

Is there a more general term than "Stereo", which implies 2: left and right? Well as it would apply to stereographic imaging, that would be "binocular", which is definitely two and only two. But there is a very strong association of that term with the paired telescopes commonly called binocular

Re: Module naming -- processing 3D JPEG files...

On 05/03/2017 04:12 AM, Smylers wrote: BC writes: I'd like some feedback and advice for naming some modules I am contemplating. Image::Stereo::MPO Image::Stereo::JPS Image::Stereo::JPG Sounds good to me — you've clearly considered this carefully, and your explanations make sense. S

Re: Module naming -- processing 3D JPEG files...

han you wanted to know. > > As for the module names, stereographic images are commonly > referred to as 3D images, but there are other associations for > the term, plus I'm guessing that "::3D::" would be a no-no for > CPAN module naming. Stereographic images are also shorthanded as > just "stereo" which is a more reasonable name length. > > ...BC > signature.asc Description: OpenPGP digital signature

Re: Module naming -- processing 3D JPEG files...

BC writes: > I'd like some feedback and advice for naming some modules I am > contemplating. > >Image::Stereo::MPO >Image::Stereo::JPS >Image::Stereo::JPG Sounds good to me — you've clearly considered this carefully, and your explanations make sense. Smylers -- http://twitter.com/S

Module naming -- processing 3D JPEG files...

se modules will do. OK -- probably more than you wanted to know. As for the module names, stereographic images are commonly referred to as 3D images, but there are other associations for the term, plus I'm guessing that "::3D::" would be a no-no for CPAN module naming. Stereographic

Re: Checking module naming

Sorry for a delayed answer, but here are my thoughts. It looks like you've published your module using the proposed naming. Your choice was a good one, in my opinion. Glad to see this hit CPAN! David On Fri, Oct 16, 2015 at 8:46 PM, wrote: > Heyas everyone, > > I'm in the process of organising

Checking module naming

Heyas everyone, I'm in the process of organising to have my very first contribution to CPAN uploaded and see that it may be prudent to ask for feedback on the names I currently have, especially as it is claiming a top-level name! I'm very open to suggestions, though I do hope these are okay! --

Re: (FYI)...Module naming collision Or mirage?

On 2013-11-13 07:39, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote: Judging by your latest CPAN release, you very much would benefit from feedback. I'm sorry, I'm a perfectionist. If I see something wrong, I don't necessarily hide things like most people. The quality of P hasn't been a major problem.

Re: (FYI)...Module naming collision Or mirage?

> The name has been dormant and unused for 11 years, yet it has > been reserved? Not quite, the module was uploaded and indexed, and was in use as example code. This is *not* a reservation. Please notice the *lack of intent* here for Math::Simple to be indexed. > If Inge wanted to use it for anyt

Re: (FYI)...Module naming collision Or mirage?

On Wed, Nov 13, 2013 at 02:29:07AM -0800, Linda A. Walsh wrote: > The name has been dormant and unused for 11 years, yet it has > been reserved? This is how first-come first-served works. He came first, so he got dibs on the name. That he appears to have come to it by accident is unfortunate, bu

Re: (FYI)...Module naming collision Or mirage?

On 2013-11-13 01:34, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote: Because of the intent. You very well already know that the indexing of Math::Simple was an accident. Right... and as soon as Sysyphus found out it was index, he had no problem letting it go to be used. In general, the permissions model (of which f

Re: (FYI)...Module naming collision Or mirage?

> Sisyphus says it's not a real module -- it is never > installed. There's no such thing as a real or unreal module. Either a package name is indexed, and then the PAUSE permissions model applies, or it's not indexed, and then there are no PAUSE permissions. Whether something gets installed or not

Re: (FYI)...Module naming collision Or mirage?

On 11/13/2013 10:04 AM, Linda W wrote: Um... but Sisyphus says it's not a real module -- it is never installed. How is this different than domain sitting? you already got a reply to this from Leon: > PAUSE automatically indexes everything it can find, unless you tell it otherwise indexed m

Re: (FYI)...Module naming collision Or mirage?

On 2013-11-12 23:54, Aldo Calpini wrote: Ingy is the original author of the first version of Inline: http://search.cpan.org/~ingy/Inline-0.44/ Sisyphus is the current maintainer. Ingy already has "first come" since 2002... Um... but Sisyphus says it's not a real module -- it is never in

Re: (FYI)...Module naming collision Or mirage?

On 11/13/2013 06:43 AM, Linda A. Walsh wrote: ??? Who is Ingy and how does he come into the picture? Ingy is the original author of the first version of Inline: http://search.cpan.org/~ingy/Inline-0.44/ Sisyphus is the current maintainer. I.e. if I just cleared the namespace ... someone else

Re: (FYI)...Module naming collision Or mirage?

On Tue, Nov 12, 2013 at 09:43:54PM -0800, Linda A. Walsh wrote: > > It will fail unless Ingy gives you permission (he has first-come > >on that namespace). > > ??? Who is Ingy and how does he come into the picture? https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_pee

Re: (FYI)...Module naming collision Or mirage?

On 2013-11-12 14:52, Leon Timmermans wrote: On Tue, Nov 12, 2013 at 11:43 PM, Linda A. Walsh mailto:perl-didd...@tlinx.org>> wrote: I've seen double listings (look at 'P', there's a really old listing for someone else who has a reference to P in their directory, but not

Re: (FYI)...Module naming collision Or mirage?

On Tue, Nov 12, 2013 at 11:43 PM, Linda A. Walsh wrote: > I've seen double listings (look at 'P', there's a really old listing for >> someone >> else who has a reference to P in their directory, but not as a module. >> > > Have a try at uploading your Math::Simple if you like. It may succeed and >

Re: (FYI)...Module naming collision Or mirage?

FYI... I got the email below from the current maintainer. They plead innocence, as it was an inherited example... ;-) On 2013-11-12 00:59, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote: So if I wanted to add Math::Simple.pm, ... Should it even be listed as a module? No, example packages should not be index

Re: Module naming collision Or mirage?

Please be precise with the terminology. Do not use the package separator when you mean the filesystem path separator. This is not a 1:1 mapping, so it matters. > So if I wanted to add Math::Simple.pm, How would it show up > and/or how would they be differentiated? It would show up as unauthorise

Module naming collision Or mirage?

When I look up Math::Simple, I find a module under Math::Simple::Simple.pm which seems to hit the index as Math::Simple So if I wanted to add Math::Simple.pm, How would it show up and/or how would they be differentiated? It's also the case that Math::Simple::Simple.pm looks like it is a demo ca

Re: Module naming and a couple other questions

Joshua, > 2. It sounds like given the single function and it's relative uniqueness, > there's no problem exporting it by default other than not being able to change > it later. For the sake of forward compatibility, I'll probably just put it in > @EXPORT_OK and require its explicit import. Beari

Re: Module naming and a couple other questions

Thank you for your replies - here's a bit more info: 1. This is not something that only runs on Win32; in fact, I doubt it will run on Win32, as this uses the WMI code from the Samba project to support WMI on non-Win32 platforms. WMI is Windows Management Instrumentation (or something like tha

Re: Module naming and a couple other questions

Hi Josh, # from Joshua Megerman on Friday 14 September 2012: >My initial inclination was to just call the >module WMIClient, but I'm starting to think that WMI::Client or some >other name would be better. The only 2 modules I currently see on >CPAN that provide similar functionality are DBD::WMI

Re: Module naming and a couple other questions

Joshua Megerman writes: > I'm a new member of PAUSE, looking to upload my first module. Hi Josh. Thanks for sharing with the Perl community. > 1. I have developed a module that provides an XS interface to the WMI > library (libasync_wmi_lib.so) that is generated by building the Zenoss WMI > soft

Module naming and a couple other questions

I originally sent this to modu...@perl.org, but got no responses. I was pointed here and am reposting them with a few tweaks. Any advice greatly appreciated! I'm a new member of PAUSE, looking to upload my first module. I ask for some advice from those who have more experience than I, as I'd lik

RFC: Module naming: User::Credentials::Provider::DBI

I have developed a module that has sort of evolved with me through several projects. On the most recent evolution it has reached a point that I think it might be generally useful as a CPAN module. The module models a user login with a DBIx::Connector back-end. Logins authenticate using both pass

Re: Module naming: postifx/dovecot/MySQL configuration

Mail::Postfixadmin seems fine to me On Tue, Dec 13, 2011 at 5:06 AM, Avi Greenbury wrote: > Hi, > > I've been working on a module which basically makes it easy to write > command-line tools for interacting with a postfixadmin[0] installation, > that is a Postfix/Dovecot mail server with virtual

Re: Module naming: postifx/dovecot/MySQL configuration

Hi Avi, * Avi Greenbury [2011-12-13 14:10]: > To me, this obviously belongs somewhere in the Mail namespace, but I'm > not really sure where it should go in that. I'm tempted to rename it > to Mail::Postfixadmin, but I don't want to give the impression that > it's somehow endorsed by that project

Module naming: postifx/dovecot/MySQL configuration

Hi, I've been working on a module which basically makes it easy to write command-line tools for interacting with a postfixadmin[0] installation, that is a Postfix/Dovecot mail server with virtual domains/users stored in MySQL. I'd like to upload it to the CPAN, and I'm after some advice on what to

Module Naming for Perl Reference Object Lookup

Hello people of module-authors! I have been working on a module which will allow one to do some relatively advanced storage and lookup mechanisms on pure Perl object references. The features are as follows: 1) Use perl objects as keys. 2) You may choose whether the database will retain a stro

Re: Taking another swing [was: New module naming]

On Tue, Nov 08, 2011 at 07:45:25AM +0100, Zbigniew Lukasiak wrote: > On Tue, Nov 8, 2011 at 2:22 AM, Aristotle Pagaltzis wrote: > > ... > > > In the real world people learn by copy-pasting code and tweaking until > > it seems to do what they wanted. Every code example should be as close > > to r

Re: New module naming

Hello Sawyer, On Tue, 8 Nov 2011 17:38:56 +0200 sawyer x wrote: > Wow this has turned into a monster thread... ouch. > > On Mon, Nov 7, 2011 at 7:42 PM, Shlomi Fish wrote: > > The problem is that using my $a and my $b will prevent the built-in $a and > > $b > > from being used and as a result

Re: New module naming

Wow this has turned into a monster thread... ouch. On Mon, Nov 7, 2011 at 7:42 PM, Shlomi Fish wrote: > Hi Sawyer, > Hey. :) The problem is that using my $a and my $b will prevent the built-in $a and > $b > from being used and as a result is a bad idea. We should make sure that > synopses and

New module naming

Hi. I've written few libraries I'd like to release on CPAN and I'm looking for some advice on how to name them. I found this idea in Head First OOA&D, chapter 5. It's somewhat like a very simple version of Key-Value Coding

Re: Taking another swing [was: New module naming]

On Tue, Nov 8, 2011 at 2:22 AM, Aristotle Pagaltzis wrote: ... > In the real world people learn by copy-pasting code and tweaking until > it seems to do what they wanted. Every code example should be as close > to real working code as possible, ideally *should* be real working code; > or else so

Re: New module naming

On Mon, Nov 7, 2011 at 12:36 PM, sawyer x wrote: > This is a case where $a and $b makes absolute sense. It is also the same > case as Perl's sort() function that uses $a and $b to indicate two values > of the same importance. ... except declaring them as lexicals still _breaks_ their use in s

Re: New module naming

On Mon, Nov 7, 2011 at 9:28 PM, Bob Parker wrote: > > In this particular case, pretty much everyone clearly understood that what > was given was a GENERIC EXAMPLE, not real code. It didn't call for code > review, comment or criticism on the use of variables or their naming. What > was requested w

Re: Taking another swing [was: New module naming]

* Bob Parker [2011-11-08 04:55]: > "Aristotle" you are, by your words and deeds in this thread, what was > known in my days in school as a bully. Apparently age and so-called > maturity has not changed that. Hating Shlomi does not justify bullying him and painting me as the bully for not letting

Re: Taking another swing [was: New module naming]

uch of the mailing list's time. If you have anything further to say, you can say it privately. -Original Message- From: Aristotle Pagaltzis Date: Tue, 8 Nov 2011 02:22:15 +0100 To: Perl Module Authors List Subject: Re: Taking another swing [was: New module naming] >* Bob Parker

Re: Taking another swing [was: New module naming]

* Bob Parker [2011-11-08 00:30]: > Clearly you are another fanboy of Shlomi's. You found me out. I am two days short of proposing gay marriage to him. > * Aristotle Pagaltzis [2011-11-07 23:50]: > >* sawyer x [2011-11-07 12:40]: > >>This is a case where $a and $b makes absolute sense. It is al

Re: Taking another swing [was: New module naming]

Clearly you are another fanboy of Shlomi's. -Original Message- From: Aristotle Pagaltzis Date: Mon, 7 Nov 2011 23:46:02 +0100 To: Perl Module Authors List Subject: Taking another swing [was: New module naming] >* sawyer x [2011-11-07 12:40]: >> * Shlomi Fish [20

Re: Politics & Personalities - was Re: New module naming

* Bob Parker [2011-11-07 22:15]: > Perhaps you are a fan of the guy, perhaps not - I don't know you. Perhaps it doesn’t even matter. Perhaps you can be a decent person to someone you dislike. > What I do know is that for the past several years, I have seen what > should have been basic and comm

Taking another swing [was: New module naming]

* sawyer x [2011-11-07 12:40]: > * Shlomi Fish [2011-11-07 18:45]: > > You shouldn't call lexical variables "$a" and "$b": > > That was a completely pointless comment, Shlomi. Only in sending it to the list instead of as a private comment, and in his way of stating it – as a do-not instead of a

Re: New module naming

> Uhm. So when would I ever use this over a simple hash? Well I used it because the application I'm working on has a data model with a lot of variation (I did this instead of creating a massive class hierarchy). The accessors are the hash key scalar string. The 'equals' and 'contains' methods are

Politics & Personalities - was Re: New module naming

From: Eirik Berg Hanssen Reply-To: Date: Mon, 7 Nov 2011 21:39:15 +0100 To: Bob Parker Cc: Shlomi Fish , Perl Module Authors List Subject: Re: New module naming > On Mon, Nov 7, 2011 at 9:28 PM, Bob Parker wrote: >> >> In this particular case, pretty much everyone cle

Re: New module naming

-Original Message- From: Shlomi Fish Date: Mon, 7 Nov 2011 19:42:35 +0200 To: sawyer x Cc: Perl Module Authors List Subject: Re: New module naming >Hi Sawyer, > >On Mon, 7 Nov 2011 13:36:58 +0200 >sawyer x wrote: > >> On Mon, Nov 7, 2011 at 10:07 AM,

Re: New module naming

On Mon, Nov 7, 2011 at 12:39 PM, Aristotle Pagaltzis wrote: > * Trystan [2011-11-06 23:30]: > > I found this idea in Head First > > OOA&D, chapter 5. It's > > somewhat like a very simple version of Key-Value > > Coding< > http://developer.apple.com/library/

Re: New module naming

* Trystan [2011-11-06 23:30]: > I found this idea in Head First > OOA&D, chapter 5. It's > somewhat like a very simple version of Key-Value > Coding

Re: New module naming

Hi Sawyer, On Mon, 7 Nov 2011 13:36:58 +0200 sawyer x wrote: > On Mon, Nov 7, 2011 at 10:07 AM, Shlomi Fish wrote: > > > > > You shouldn't call lexical variables "$a" and "$b": > > > > That was a completely pointless comment, Shlomi. > > He's trying to showcase an action on two objects that

Re: New module naming

> What about Object::KVC, Object::KVC::String, Object::KVC::List? KVC it is. I had actually been considering that. In the Object::Generic documentation the author says his module should have been in the "Class::" namespace. What is the difference between the Object:: namespace and Class:: name

Re: New module naming

On Mon, Nov 7, 2011 at 10:07 AM, Shlomi Fish wrote: > > You shouldn't call lexical variables "$a" and "$b": > That was a completely pointless comment, Shlomi. He's trying to showcase an action on two objects that have the exact same level of importance and relevance. Calling them $a and $b is t

Re: New module naming

What about Object::KVC, Object::KVC::String, Object::KVC::List? Trystan wrote: I found this idea in Head First OOA&D , chapter 5. It's somewhat like a very simple version of Key-Value Coding

Re: New module naming

Hi Trystan, On Sun, 6 Nov 2011 16:28:03 -0600 Trystan wrote: > Hi. I've written few libraries I'd like to release on CPAN and I'm looking > for some advice on how to name them. > > I found this idea in Head First OOA&D, > chapter 5. It's somewhat like a v

New module naming

Hi. I've written few libraries I'd like to release on CPAN and I'm looking for some advice on how to name them. I found this idea in Head First OOA&D, chapter 5. It's somewhat like a very simple version of Key-Value Coding

Re: Module Naming Suggestion - Carp from somewhere else

Have you talked to the maintainer of Carp about this? It might be best to just suggest it as a new feature in Carp itself. Otherwise, Carp::Whence or something might seem reasonable to me. On Sat, Mar 5, 2011 at 4:11 AM, Paul LeoNerd Evans wrote: > (To copypaste > http://leonerds-code.blogspot.

Module Naming Suggestion - Carp from somewhere else

(To copypaste http://leonerds-code.blogspot.com/2011/03/carp-from-somewhere-else.html ): Carp provides two main functions, carp and croak, as replacements for core Perl's warn and die. The functions from Carp report the file and line number slightly differently from core Perl; walking up the call

Re: Module naming - Test::Import::DontRun

Hi all, It occurs to me that the uses for this could extend outside testing. Looking at CPAN, the root namespace 'Include' already exists, so Include::DontRun would be a viable name, and seems pretty descriptive to me. Anyone got any objections? I've handled the __DATA__ and __END__ cases now.

Re: Module naming - Test::Import::DontRun

When developing code to include One might think it intolerably rude To use words ungrammatical As a method pragmatical To avoid compilation being screwed :-P On 8 October 2010 00:13, Paul Johnson wrote: > On Thu, Oct 07, 2010 at 12:36:41PM +0100, Charles Colbourn wrote: > >> Test::Include::DontR

Re: Module naming - Test::Import::DontRun

On Thu, Oct 7, 2010 at 4:13 PM, Paul Johnson wrote: > On Thu, Oct 07, 2010 at 12:36:41PM +0100, Charles Colbourn wrote: > > > Test::Include::DontRun > > I'll just point out that any name which includes DontRun rather than > Don't::Run has sold its soul and should probably start with > Com::Really

Re: Module naming - Test::Import::DontRun

On Thu, Oct 07, 2010 at 12:36:41PM +0100, Charles Colbourn wrote: > Test::Include::DontRun I'll just point out that any name which includes DontRun rather than Don't::Run has sold its soul and should probably start with Com::ReallyBigCorporation::Enterprise:: Then I'll duck (low) and I will run.

Re: Module naming - Test::Import::DontRun

On Thu, Oct 7, 2010 at 10:22 AM, Charles Colbourn < charles.colbo...@googlemail.com> wrote: > It works very simply, by wrapping the source of 'myscript.pl' in > "{last; }'. Well, as it seems it does no ->import(), but just compiles the code ... Test::LegacyScript::Compile? > There's som

Re: Module naming - Test::Import::DontRun

--- Forwarded message -- > From: Charles Colbourn > Date: 7 October 2010 10:10 > Subject: Re: Module naming - Test::Import::DontRun > To: ebhans...@cpan.org > > > @Eirik > >>> >>> There's some complex and potentially slightly >>> fragile

Fwd: Module naming - Test::Import::DontRun

-- Forwarded message -- From: Charles Colbourn Date: 7 October 2010 10:10 Subject: Re: Module naming - Test::Import::DontRun To: ebhans...@cpan.org @Eirik >> >> There's some complex and potentially slightly >> fragile stuff to handle @EXPORT if you want

Re: Module naming - Test::Import::DontRun

OK, I get what you want to do. I have seen this before. My brains being what they are lately, I don't remember where but it was not so long ago. Maybe Andy maybe someone else. Maybe even you ;) So before you go further, you can, if you so wish, look around a bit. I'm sure that other with better

Re: Module naming - Test::Import::DontRun

Mea Culpa - it wasn't a very clear description. OK, so perhaps you have a script like this: ###myscript.pl### doStuff(); doOtherStuff(); sub doStuff{ # things that need testing } sub doOtherStuff{ # things you don't want to run } __END__ and you don't have the option of wrapping the top leve

Re: Module naming - Test::Import::DontRun

I must admit that I didn't get what you mean. Care to enlighten me with a piece of code, some flow, anything that doesn't make me feel stupid. Nadim.

Module naming - Test::Import::DontRun

Hi, I have a module that attempts to import scripts/modules without executing anything in top level scope, so that test scripts can import their functions/methods and test them. Is Test::Import::DontRun a sufficiently descriptive name? I also thought about Test::DontRun, and Test::DontExecute, but

Re: Module Naming

Message-- From: nadim khemir To: module-authors@perl.org Sent: Oct 5, 2010 2:58 AM Subject: Re: Module Naming You should have what type of device in the name too. The fact that it works with serial port is not interesting and can be made clear in a sub module if multiple communication medium e

Re: Module Naming

Aurora is a type of inverter and serial is type of aurora however if inheriting Device::Serial put that first Device::Serial::Inverter::Aurora --Original Message-- From: nadim khemir To: module-authors@perl.org Sent: Oct 5, 2010 2:58 AM Subject: Re: Module Naming You should have what

Re: Module Naming

You should have what type of device in the name too. The fact that it works with serial port is not interesting and can be made clear in a sub module if multiple communication medium exist. Device::Inverter::Aurora Be more specific in the top classes if you can. The idea is to have a name for

Re: Module Naming

If not Device::Aurora Perhaps something along the lines of Device::SerialPort::Aurora ? Or Device::Serial::Protocol::Aurora (except that the module handles all the SerialPort stuff too)

Module Naming

Hi there. Was reading the information available at the PAUSE website and it suggested getting your opinions for the naming of the module I want to upload It's "working title" is Device::Aurora. It provides the protocol and constants required for communicating with a Power-One Aurora Invert

Re: RFC: Automated Assistance with Module Naming and Projection

[Yes, my reply is sort of off topic] On Tue, Aug 24, 2010 at 06:02:06PM -0700, Xiong Changnian wrote: > On Wed, 2010-08-25 at 01:13 +0200, nadim khemir wrote: > You may find the register in which I write overly formal. I don't wish > to insult anyone who may be more comfortable writing in another

Re: RFC: Automated Assistance with Module Naming and Projection

Xiang, friend, just drop it. The whole thing, you are not getting popular and I would like you and your modules to become popular. You got help. We can't give you more. Any of those who answered you have 20+ years experience. Don't make yourself a nOOb. We all welcome you but the first thing you

Re: RFC: Automated Assistance with Module Naming and Projection

David++ +++ David Cantrell [Wed, Aug 25, 2010 at 11:47:05AM +0100]: > On Tue, Aug 24, 2010 at 03:37:13PM -0700, Xiong Changnian wrote: > > > I'd love to discuss the technical aspects but first, like all projects, > > this one requires a name (and is not yet available to suggest one for > > itsel

Re: RFC: Automated Assistance with Module Naming and Projection

I find mid-development changes to the project name drastically disruptive. Perhaps I am, indeed, doing it wrong. But I will not drag another project through such a trial; from now on, the name must be settled very early in development. I'm sorry to hear this precludes guidance from this list. I hav

Re: RFC: Automated Assistance with Module Naming and Projection

On Tue, Aug 24, 2010 at 03:37:13PM -0700, Xiong Changnian wrote: > I'd love to discuss the technical aspects but first, like all projects, > this one requires a name (and is not yet available to suggest one for > itself!) The solution is simple. Write it. Then use it to name itself. Good luck

  1   2   3   >