9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Why does Acme only show text?
Date: Wed, 15 Jul 2009 22:07:41 +0100	[thread overview]
Message-ID: <20090715220741.4835ddb4.eekee57@fastmail.fm> (raw)
In-Reply-To: <56a297000907151342x334e7793ubfedb791a62f2bd8@mail.gmail.com>

On Wed, 15 Jul 2009 22:42:20 +0200
Noah Evans <noah.evans@gmail.com> wrote:

> http://9fans.net/archive/2008/05/6

Good to see this brought up. Whitespace may be the most comfortably readable means of indicating flow, but it's fragile. Better, IMHO, is delimiters with plenty of space around them, but even then they do intrude. Currently I like Q where parentheses can be used if necessary but a couple of syntactic tricks are used to keep them to the minimum and whitespace has some meaning but (IIRC) not over-much.

I find the best thing to do with languages with delimeters is to run code through a code formatter often. I'm using Gnu indent for C code (especially valuable when dealing with Gnu C :) ), is there a similar tool for Plan 9?

> 
> On Wed, Jul 15, 2009 at 10:29 PM, Jason Catena<jason.catena@gmail.com> wrote:
> > Devon's anecdote is along the lines of my position.  I'm sure there's
> > a paper somewhere that counts parenthesis versus whitespace errors,
> > but I haven't yet read it.  I have programmed Lisp and Haskell (at two
> > extremes), and from this experience at least much prefer whitespace to
> > parentheses.  In addition, I rely on design theory (esp. Tufte et al
> > on his web site) that reducing clutter aids comprehension, and
> > delimiters very much seem clutter to me.
> >
> > Jason Catena
> >
> >
>

-- 
Ethan Grammatikidis

Those who are slower at parsing information must
necessarily be faster at problem-solving.



  parent reply	other threads:[~2009-07-15 21:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  1:58 Jason Catena
2009-07-15  4:36 ` Rob Pike
2009-07-15  5:02   ` David Leimbach
2009-07-15 13:11   ` Charles Forsyth
2009-07-16  9:58   ` cej
2009-07-16 10:41     ` mattmobile
2009-07-16 12:11     ` michael block
2009-07-16 12:29       ` cej
2009-07-15  9:25 ` Paul Donnelly
2009-07-15 12:22   ` Ethan Grammatikidis
2009-07-15 15:32     ` cej
2009-07-15 15:44       ` Ethan Grammatikidis
2009-07-15 17:00         ` John Floren
2009-07-15 18:24           ` Francisco J Ballesteros
2009-07-15 18:26           ` Steve Simon
2009-07-15 18:59             ` David Leimbach
2009-07-15 19:07               ` John Floren
2009-07-15 19:27                 ` David Leimbach
2009-07-15 20:58                 ` Chad Brown
2009-07-15 21:07                   ` John Floren
2009-07-15 19:54               ` Jason Catena
2009-07-15 19:59                 ` erik quanstrom
2009-07-15 20:05                   ` andrey mirtchovski
2009-07-15 20:14                   ` Devon H. O'Dell
2009-07-15 20:29                     ` Jason Catena
2009-07-15 20:42                       ` Noah Evans
2009-07-15 20:51                         ` David Leimbach
2009-07-15 21:27                           ` Ethan Grammatikidis
2009-07-15 23:31                             ` Jason Catena
2009-07-15 21:07                         ` Ethan Grammatikidis [this message]
2009-07-15 21:12                           ` erik quanstrom
2009-07-15 21:32                             ` Ethan Grammatikidis
2009-07-15 20:41                     ` Lyndon Nerenberg
2009-07-15 21:00     ` Federico G. Benavento
2009-07-15 21:14       ` David Leimbach
2009-07-16  8:51     ` Paul Donnelly

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=20090715220741.4835ddb4.eekee57@fastmail.fm \
    --to=eekee57@fastmail.fm \
    --cc=9fans@9fans.net \
    /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.
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).