Xref: utzoo comp.sys.mac:19450 comp.sys.mac.programmer:2134
Path: utzoo!attcan!uunet!husc6!bbn!oberon!pollux.usc.edu!kurtzman
From: kurtzman@pollux.usc.edu (Stephen Kurtzman)
Newsgroups: comp.sys.mac,comp.sys.mac.programmer
Subject: Re: LSP 2.0
Keywords: features editor
Message-ID: <11689@oberon.USC.EDU>
Date: 18 Aug 88 21:21:40 GMT
References: <450@umn-d-ub.D.UMN.EDU> <5116@husc6.harvard.edu> <11864@steinmetz.ge.com> <64658@sun.uucp>
Sender: news@oberon.USC.EDU
Reply-To: kurtzman@pollux.usc.edu (Stephen Kurtzman)
Organization: University of Southern California, Los Angeles, CA
Lines: 16

In article <64658@sun.uucp> landman@sun.UUCP (Howard A. Landman) writes:

>Hmmm.  I've worked at two companies where it was part of the coding
>standards that you never put more than one statement on a line.  Of
>course, in C it's possible to cheat:
>	i = 1, j = 2, k = 5, m = 12;
>The above is technically one statement.

A looser interpretation of the one statement per line rule is
one functional unit per line. The variables assignments
used in your example is a good example of a single functional
unit. Putting these all on one line is not unlike listing all
of the arguments to a function together on a single line. That is,
in some contexts the variable assignments can be viewed as the
initialization of parameters used in the following block of
code.