Re: Apologies
On Wed, 25 Aug 2010 18:39:48 -0700, Xiong Changnian wrote: > Please allow me to stress my regret at disturbing your peace by > writing in a mode you find offensive. The more I seek to avoid > offense, the more offensive I become. I lament my inability to > express courtesy in a form you might find fair. I refrain from > further participation in this list. If anyone should require > anything from me, for any reason, please email me directly. I shall > be grateful to be your most obliging servant. While your style of writing may indeed be excessively formal or flowery, as exemplified by the above, I think you deserve just as much apology from those members of the list who have chosen to respond in such an insulting manner. Yes, you would do well to write more concisely, but you don't warrant the lambasting you have received. Nadim wrote: > It may sound strange but if you [can't] get the humor and > sensibility the Perl comunity has, it may be better to find another > one. This is not just Software. It is social, living, fun. Just how much humour and sensibility have you shown here, Nadim? You're not sounding particularly social or fun. Now, back to topic: Yes, it is certainly an enormous pain to have to rename modules once they have been released to CPAN. However, starting with a generic placeholder name allows you write some code and get a feel for how it actually works, which may in turn inspire a good name. If nothing else, it should give a much clearer impression of what the module does and how, than a long-winded description, no matter how well written. This is what you should be bringing to the modules list. It will still likely be inconvenient to rename at this stage, but not as difficult as you seem to have found. Maybe if you explain what problems you had with previous renames, we could give some useful advice about that. -- Peter Haworth| I unicycled 140 miles coast to coast for BHF p...@edison.ioppublishing.com | Please sponsor me at justgiving.com/pmh1wheel "The usability of a computer language is inversely proportional to the number of theoretical axes the language designer tries to grind." -- Larry Wall This email (and attachments) are confidential and intended for the addressee(s) only. If you are not the intended recipient please notify the sender, delete any copies and do not take action in reliance on it. Any views expressed are the author's and do not represent those of IOP, except where specifically stated. IOP takes reasonable precautions to protect against viruses but accepts no responsibility for loss or damage arising from virus infection. For the protection of IOP's systems and staff emails are scanned automatically.” Institute of Physics Registered in England under Registration No 293851 Registered Office: 76/78 Portland Place, London W1B 1NT
Re: Name for "EscapeCage"
On Wed, 27 Jun 2007 01:32:54 -0700, Eric Wilhelm wrote: > # from Bill Ward on Tuesday 26 June 2007 11:39 pm: > >how about String::Cage? > > Or maybe String::Muzzle. Trapped, Quarantine, Shackled. > > Sounds like a useful module. Sort of an explosive Hungarian > notation. Indeed. I tried writing something similar-sounding a while ago, which I called IO::Hungarian. I didn't get very far, though. -- Peter Haworth [EMAIL PROTECTED] File not found. Should I fake it? (Y/N)
RE: Name for module to construct URI from named params?
On Wed, 5 Oct 2005 02:44:33 -0500 (CDT), Dave Rolsky wrote: > On Wed, 5 Oct 2005, Orton, Yves wrote: > > FromHash seems inappropriate, as you aren't actually using a hash there. > > Excellent point! Um, how about ... > > URI::NamedParams > URI::Constructor > URI::Creator > > The first is clearest, but people always hate it when a module describes > its interface in the name (like Foo::OO), although maybe in this case > that's ok because that's really the whole point of the module, to provide > an alternate to the existing URI interface. How about this? URI::Construct::named_params(scheme => 'http', ...); which would allow extension along the lines of URI::Construct::foo($bar,$baz) -- Peter Haworth [EMAIL PROTECTED] "I defy you to use the documentation to understand ... the ANSI C++ draft standard. It's not for nothing that comp.lang.std.c++ has a FAQ sixteen times the thickness of the Hong Kong phone book." -- Felix Gallo
Re: DRMAA namespace (DRMAA - Distributed Resource Manager Application API)
On Wed, 24 Mar 2004 16:52:13 +0100, Dariush Pietrzak wrote: > > On Wed, 24 Mar 2004 07:27:38 -, IvorW wrote: > > When I see DRM, I think "Digital Rights Management," so having a more > > descriptive name would be less confusing. > and not Direct Rendering Manager? Maybe, if I didn't work for a publisher :-) -- Peter Haworth [EMAIL PROTECTED] "Ack, i don't believe I just used the phrase 'the blog scene', i need to leave now to either wash my fingers for a couple of hours or see if the daily mail need a new internet correspondent." -- Greg McCarroll
Re: DRMAA namespace (DRMAA - Distributed Resource Manager Application API)
On Wed, 24 Mar 2004 07:27:38 -, IvorW wrote: > Why look to a new top level namespace? Who else has heard of, or would > think of DRM or DRMAA if they want scheduling. When I see DRM, I think "Digital Rights Management," so having a more descriptive name would be less confusing. > Consider Schedule::. This is where I think your module belongs. > > e.g. Schedule::DRMAA, Schedule::DRMAA::Simple, Schedule::DRM::SGE What he said. -- Peter Haworth [EMAIL PROTECTED] "People don't buy our products because they want a 1/2 inch drill, they buy our products because they want a 1/2 inch hole." -- reportedly, some exec at Black and Decker
Re: cpan name spaces (was: Re: Re3: Re: How about class Foo {...} definition for Perl? )
On Mon, 19 Jan 2004 11:03:05 -0600 (CST), Chris Josephes wrote: > On Mon, 19 Jan 2004, Mark Stosberg wrote: > > And what happens when module author gets married and get a new > > hyphenated last name? > > How often do CPAN ids really change? I doubt that an extablished author > would extend his given name change to his CPAN id. Twice that I can remember: JAPHY -> JPINYAN CTWETEN -> CWEST -- Peter Haworth [EMAIL PROTECTED] "Jarkko suggested throwing out [the unicode directory] (with a caution that attempting to use Unicode stuff would make demons fly out of your nose.)" -- Simon Cozens
Re: RFC: OAI::Harvester
On Mon, 7 Jul 2003 12:25:46 -0400, Ed Summers wrote: > The OAI::Harvester disto is made up of 14 separate packages. For the sake > of preserving my existing namespaces I'd like to upload these into a > top-level namespace of OAI::, but Metadata:: could work as well. Looks like you've gone ahead with Net::OAI::, which seems reasonable to me. Of course, strictly speaking, it should be Net::OAI::PMH::, but whenever I've heard people talking about OAI, they always leave the PMH bit off, which suits me, given my initials :-) -- Peter Haworth [EMAIL PROTECTED] "ACRONYM = A Capitalized Representation Of Names You Memorize" -- Bartman
