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:27:58 +0100 [thread overview]
Message-ID: <20090715222758.28371a78.eekee57@fastmail.fm> (raw)
In-Reply-To: <3e1162e60907151351n1e88a15ue70da5cdd83317b4@mail.gmail.com>
On Wed, 15 Jul 2009 13:51:02 -0700
David Leimbach <leimy2k@gmail.com> wrote:
> 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
The linked post pointed out there are times when barely-visible errors are not caught and go on to cause big problems. That's pretty nasty.
>
> 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"
Huh, so this Haskell syntax actually prevents you from indenting something that would be indented in any other language. Okay...
>
> 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.
It sure doesn't look comfortable to me. Strange semicolon placement for one thing. Do the braces have to be on the same lines as the code like that? Could it be written like this?:
do
{
x <- foo;
y <- bar
}
That's readable to my eyes, but looks like it may be quite different to the first form.
--
Ethan Grammatikidis
Those who are slower at parsing information must
necessarily be faster at problem-solving.
next prev parent reply other threads:[~2009-07-15 21:27 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 [this message]
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=20090715222758.28371a78.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).