9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Why does Acme only show text?
Date: Wed, 15 Jul 2009 13:51:02 -0700	[thread overview]
Message-ID: <3e1162e60907151351n1e88a15ue70da5cdd83317b4@mail.gmail.com> (raw)
In-Reply-To: <56a297000907151342x334e7793ubfedb791a62f2bd8@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

On Wed, Jul 15, 2009 at 1:42 PM, Noah Evans <noah.evans@gmail.com> wrote:

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


Haskell *will* tell you errors that don't make any sense (at least GHC
errors) when you don't have things like this done properly

do x <- foo
y <- bar

the y <- bar must be directly under the x on the previous line or it's a
syntax error, and the error you get from GHC is "the last statement of a do
construct must be an expression"

not

"dude, you suck at indenting code, and should have used Emacs to keep track
of it, because nothing else does the job right".

Luckilly Haskell will let you ignore "layout" and do the following:

do { x <- foo
; y <- bar }

However, I don't see enough of this style code to feel comfortable writing
anything I'd plan to share with anyone and expect them to feel ok reading
it.

Dave


> <http://9fans.net/archive/2008/05/6>
>
> 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
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 2423 bytes --]

  reply	other threads:[~2009-07-15 20:51 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 [this message]
2009-07-15 21:27                           ` Ethan Grammatikidis
2009-07-15 23:31                             ` Jason Catena
2009-07-15 21:07                         ` Ethan Grammatikidis
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=3e1162e60907151351n1e88a15ue70da5cdd83317b4@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --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).