On Wed, 9 Apr 2003, Michael Campbell wrote:

> I know we're delving into holy ground here, but what makes you think
> whitespace after a function call and before the left paren is a c'ism?

gnu coding standards.

~ > cat foo.c
strlen("foobar");

~ > cat foo.c | indent
strlen ("foobar");

~ > man indent
....
DESCRIPTION
       ...
       In version 1.2 and more recent versions, the GNU style  of
       indenting is the default.
....


i love indent, defaults, gnu, and standards.  ;-)

-a


>
> The style guides I can come up with generally favor *NO* whitespace
> after the function name when making a call.  The earliest
> (chronologically) style guide I remember (and can find) is the Henry
> Spencer Indian Hill one
> (http://www.chris-lott.org/resources/cstyle/indhill-annot.html), and
> while it doesn't explicitly say one way or the other, has in its
> examples the mathematical (i.e. f(x)) style shown.
>
> Later versions of the Indian Hill guide do show a mixture of
> mathematical style and not in various examples but never say one way
> or the other that I can find.  Ellemtel (granted, C++ here) says
> explicitly to "Always write the left parenthesis directly after a
> function name" (though this is I think implied for the declaration,
> not the call.)
>
> I only ask because I've only come to see this stylistic convention
> (in languages that require parens for function/method/message calls)
> recently; like in the last 8-9 years.  Prior to that it was almost
> exclusively the mathematical style.
>
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
> http://tax.yahoo.com
>
>

--
  ====================================
  | Ara Howard
  | NOAA Forecast Systems Laboratory
  | Information and Technology Services
  | Data Systems Group
  | R/FST 325 Broadway
  | Boulder, CO 80305-3328
  | Email: ahoward / fsl.noaa.gov
  | Phone:  303-497-7238
  | Fax:    303-497-7259
  ====================================