From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A new language for Plan 9
Date: Thu, 1 May 2008 22:19:11 -0400 [thread overview]
Message-ID: <31D2A9A4-E6AD-4D66-AE2A-6168A3F09D9C@mac.com> (raw)
In-Reply-To: <7359f0490805011852k64a52a01k1efc1e6aba8b030c@mail.gmail.com>
On May 1, 2008, at 9:52 PM, Rob Pike wrote:
> Indentation by white space is a very bad idea in my experience.
> Superficially attractive but ultimately very dangerous. I once spent a
> couple of days tracking down a bug caused by a source-to-source code
> tool that broke a major program because the code it was injecting into
> had indented one more space, causing the injecting code to break the
> control flow. It was nearly impossible to track down.
>
This scenario is why I decided to require hard tabs as indents. You
can't use a space. But a space halts the indentation, so the problem
is still there. The next version will just ignore spaces, and treat
the first non-whitespace character as the beginning of a line.
> I have lots of other examples of lesser disasters. As code grows,
> white space indentation becomes ever more problematic. It's a
> maintenance disaster.
>
> Put it this way: It's unwise to make program structure depend on
> invisible characters.
There's a language made entirely of said invisible characters, called
Whitespace. It's esoteric, but it works. And Python, which has the
same style, is a phenomenal success. Whether or not indentation works
relies on the programmer.
next prev parent reply other threads:[~2008-05-02 2:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 1:23 Pietro Gagliardi
2008-05-02 1:26 ` erik quanstrom
2008-05-02 2:21 ` Pietro Gagliardi
2008-05-02 2:34 ` Pietro Gagliardi
2008-05-07 9:24 ` Matt Erickson
2008-05-08 2:22 ` Pietro Gagliardi
2008-05-11 23:04 ` Pietro Gagliardi
2008-05-02 1:52 ` Rob Pike
2008-05-02 1:12 ` Federico G. Benavento
2008-05-02 2:22 ` Pietro Gagliardi
2008-05-02 1:53 ` Rob Pike
2008-05-02 2:19 ` Pietro Gagliardi [this message]
2008-05-02 3:22 ` Robert William Fuller
2008-05-02 12:34 ` Chad Dougherty
2008-05-02 14:43 ` Robert William Fuller
2008-05-03 14:07 ` David Arnold
2008-05-03 15:47 ` lucio
2008-05-03 23:28 ` Skip Tavakkolian
2008-05-03 23:32 ` Bruce Ellis
2008-05-03 23:50 ` Pietro Gagliardi
2008-05-04 2:43 ` Eric Van Hensbergen
2008-05-04 5:16 ` Steve Simon
2008-05-04 5:42 ` Bruce Ellis
2008-05-04 7:42 ` John Stalker
2008-05-04 7:48 ` Steve Simon
2008-05-04 7:57 ` lucio
2008-05-04 12:18 ` Bruce Ellis
2008-05-04 13:48 ` Pietro Gagliardi
2008-05-04 15:03 ` Eric Van Hensbergen
2008-05-05 1:45 ` Pietro Gagliardi
2008-05-05 2:24 ` andrey mirtchovski
2008-05-05 3:58 ` erik quanstrom
2008-05-05 10:16 ` Pietro Gagliardi
2008-05-05 4:32 ` Bruce Ellis
2008-05-02 4:25 ` ron minnich
2008-05-02 4:41 ` John Barham
2008-05-02 4:54 ` ron minnich
2008-05-02 5:01 ` John Barham
2008-05-02 4:39 ` John Barham
2008-05-02 5:07 ` andrey mirtchovski
2008-05-02 12:12 ` erik quanstrom
2008-05-02 5:07 ` John Barham
2008-05-02 12:07 ` erik quanstrom
2008-05-02 7:49 ` John Stalker
2008-05-02 8:42 ` Bakul Shah
2008-05-02 9:24 ` Martin Neubauer
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=31D2A9A4-E6AD-4D66-AE2A-6168A3F09D9C@mac.com \
--to=pietro10@mac.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).