zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: zsh coding standards
Date: Mon, 29 Nov 2004 16:52:15 +0000	[thread overview]
Message-ID: <200411291652.iATGqFMM022054@news01.csr.com> (raw)
In-Reply-To: <20041129164253.GA539@blorf.net>

Wayne Davison wrote:
> Speaking of coding standards, it has only been fairly recently (perhaps
> this year?) that you have started to put braces on the line following an
> "if", "while", etc.  Is this a conscious decision to change zsh's coding
> style?  I personally prefer seeing the braces on the same line as the
> controlling statement (except for the start of a function).

It's because that's how we do it at CSR, and switching between the two
is too complicated for me.  It's not intentional.

> Use "{}" on an empty loop instead of ";" to make it more obvious that no
> looping statements follow.

I think this is mostly done by putting the ";" on the next line, which
makes the intention clear enough.  Putting a ";" on the same line
immediately after the loop statement is certainly more bug-prone.

> Attached is a patch of the zchdir() function that contains only the style
> changes mentioned above.  They won't be committed unless agreement is
> reached that they would be a good thing.

Anything that makes it more readable is fine by me, although it's quite
hard to enforce this sort of nicety.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  reply	other threads:[~2004-11-29 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 11:57 [bug] fd leak when zchdir to TOOLONG paths Stephane Chazelas
2004-11-29 12:10 ` Peter Stephenson
2004-11-29 15:34   ` OT: Coding (was Re: [bug] fd leak) Bart Schaefer
2004-11-29 16:42   ` zsh coding standards Wayne Davison
2004-11-29 16:52     ` Peter Stephenson [this message]
2004-11-29 16:57     ` Alexandre Duret-Lutz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200411291652.iATGqFMM022054@news01.csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).