[Dev] Coding Guidelines

[Ted Leung]

And most other Python code is formatted this way.  +1 for paren 
immediately after the function name.

Ted

On Nov 19, 2004, at 9:37 AM, Bryan Stearns wrote:

> Guido prefers the paren immediately following the function name:
> http://www.python.org/doc/essays/styleguide.html. (So do I, but I 
> think his
> +1 means more than mine in this case.)
>
> ...Bryan
>
> -----Original Message-----
> From: dev-bounces at osafoundation.org 
> [mailto:dev-bounces at osafoundation.org]
> On Behalf Of Heikki Toivonen
> Sent: Thursday, November 18, 2004 7:58 PM
> To: 'OSAF Development'
> Subject: Re: [Dev] Coding Guidelines
>
> Donn Denman wrote:
>> I've been using John's syntax of having a space before the paren, and
>> at first found it hard to write, but now have gotten used to it.  I
>> have always found it somewhat easier to read, though it may takes a
>> bit time to get used to it.
>
> I prefer the paren immediately following the function name. It is 
> easier to
> find using tools (I find readability about the same). You can also 
> easily
> have tools find functions vs variables. Having the space can also 
> cause an
> automatic line wrap to appear at a weird place (for example when you 
> copy
> sample code to web).
>
> -- 
>    Heikki Toivonen
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev
>
----
Ted Leung                 Open Source Applications Foundation (OSAF)
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42