Name od builtin functions: is there a rule ??

Gilles 'CactusMan' Boccon-Gibod (gilles@la.tce.com)
19 Apr 1995 21:47:13 GMT

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Ray Matthieu: "how reliable is freeze?"
Previous message: Reimer Behrends: "Re: os.listdir('*.py')"
Next in thread: Eric Daniel: "Re: Name od builtin functions: is there a rule ??"

I just finished reading the python docs. It seems to be a very nice
language, but what bothers me is that I'm unable to find any rule or
convention for the naming of the builtin fucntions. Is there a reason,
or have functions been added one after an other without care of having
a consistent naming convention? Even though it does not change the
functionalities or semantics of the language, it is a bit irritating.
Examples:
some functions have underscores between words (has_keys, or exc_traceback,
...),
some functions have no underscores between words (fetchcolor, expandtabs,
...)
some functions have no underscors but Uppercases for the beginning of
the words (GetPitch, Write, UDPCreate, ...)

Can someone explain ?

--
=========================================================================
           /  ) (  \    Oooo. | Gilles Boccon-Gibod   | gilles@la.tce.com
 .oooO    /  /   \  \   (   ) | 1720 Pacific Av, #301 | enst@netcom.com  
 (   )   /  (     )  \   ) /  | Los Angeles, CA 90291 | 'Bok' on IRC     
  \ (   (    )   (    ) (_/   |------------------------------------------
   \_)   oooO0   0Oooo        | Hop, et Hop, et Hop, et dans le baba.    
=========================================================================

Next message: Ray Matthieu: "how reliable is freeze?"
Previous message: Reimer Behrends: "Re: os.listdir('*.py')"
Next in thread: Eric Daniel: "Re: Name od builtin functions: is there a rule ??"