RE: Define consistent and standard

2000-08-11 Thread Garrett Goebel
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > What I was trying to get across was that if you're storing > more than one email address per person, you might use > %email_addresses and therefore $email_addresses{Skud}, whereas > if you're limiting it to one email address per person, it w

Re: Define consistent and standard

2000-08-10 Thread skud
On Mon, Aug 07, 2000 at 05:39:02PM +0200, Bart Lateur wrote: > >>* Hash names should be written so that looking up an element reads clearly: >> $email_address{Skud} reads as "the email address of Skud" >>* Hashes with scalars as values should have singular names: >> my $address = $email_

Re: Define consistent and standard

2000-08-07 Thread Bart Lateur
On Sun, 6 Aug 2000 01:13:22 +1000, [EMAIL PROTECTED] wrote: >* Variables are things are nouns. Give them noun names. > $name, $total, $input >* Plural variables should have plural names > @employees, @items, %contact_details Hmmm... >* Hash names should be written so that looking up

RE: Define consistent and standard

2000-08-07 Thread Garrett Goebel
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > * Plural variables should have plural names > @employees, @items, %contact_details > * Hash names should be written so that looking up an element > reads clearly: > $email_address{Skud} reads as "the email address of Skud" Should

Re: Define consistent and standard

2000-08-05 Thread skud
On Fri, Aug 04, 2000 at 03:21:37AM -0800, Michael Fowler wrote: >On Fri, Aug 04, 2000 at 10:37:02AM +0100, Leon Brocard wrote: >> Michael Fowler sent the following bits through the ether: >> >> > Personally, I think FindBin is a bit of a sore thumb. Its name, the >> > capitalization of its varia

Re: Define consistent and standard

2000-08-04 Thread Michael Fowler
On Fri, Aug 04, 2000 at 02:21:03PM +0200, Gisle Aas wrote: > Michael Fowler <[EMAIL PROTECTED]> writes: > > I'm going to wait until Gisle Aas puts out his RFC, and bat it around at > > that point. > > I don't think I promised to do anything. You must be waiting for > somebody else. Oh, I must'v

Re: Define consistent and standard

2000-08-04 Thread Gisle Aas
Michael Fowler <[EMAIL PROTECTED]> writes: > On Fri, Aug 04, 2000 at 10:37:02AM +0100, Leon Brocard wrote: > > Michael Fowler sent the following bits through the ether: > > > > > Personally, I think FindBin is a bit of a sore thumb. Its name, the > > > capitalization of its variable names > >

Re: Define consistent and standard

2000-08-04 Thread Graham Barr
On Fri, Aug 04, 2000 at 05:20:33AM -0600, Tom Christiansen wrote: > Agreed completely. This was a complaint I heard at TPC: that the > core modules were inharmonious in this regard, and that they thus > needed homogenization. It's hard to back-fit changes, so it's more > important that naming co

Re: Define consistent and standard

2000-08-04 Thread Tom Christiansen
>I think no matter what is decided, consistency-wise, someone is going to be >unhappy with it. If we use DumpCore() the C programmers won't like us, >dump_core() and the C++ and Java programmers will throw fits. I think the >best thing we can do is decide on what -Perl- programmers want. >Unfor

Re: Define consistent and standard

2000-08-04 Thread Michael Fowler
On Fri, Aug 04, 2000 at 10:37:02AM +0100, Leon Brocard wrote: > Michael Fowler sent the following bits through the ether: > > > Personally, I think FindBin is a bit of a sore thumb. Its name, the > > capitalization of its variable names > > I suppose we could try and define some Perl Naming Con

Re: Define consistent and standard

2000-08-04 Thread Tom Christiansen
>Michael Fowler sent the following bits through the ether: >> Personally, I think FindBin is a bit of a sore thumb. Its name, the >> capitalization of its variable names >I suppose we could try and define some Perl Naming Conventions - ie >instead of DumpCore() we should have dump_core(). Agr

Re: Define consistent and standard

2000-08-04 Thread Leon Brocard
Michael Fowler sent the following bits through the ether: > Personally, I think FindBin is a bit of a sore thumb. Its name, the > capitalization of its variable names I suppose we could try and define some Perl Naming Conventions - ie instead of DumpCore() we should have dump_core(). This'll re

Re: Define consistent and standard

2000-08-04 Thread Graham Barr
On Thu, Aug 03, 2000 at 01:59:08PM -0500, Garrett Goebel wrote: > What constitutes consistent API's and standard naming conventions? In due course I will be posting an RFC along the lines of "The modules in the stdlib are not consistent with each other". I think many will be surprised at how diff

Re: Define consistent and standard

2000-08-03 Thread Michael Fowler
On Thu, Aug 03, 2000 at 01:59:08PM -0500, Garrett Goebel wrote: > What constitutes consistent API's and standard naming conventions? I'm not sure what constitutes consistence in Perl 5, so it's difficult to plop down an RFC saying "this is consistent, do this". What modules display a kind of con