This is the mail archive of the
guile@cygnus.com
mailing list for the Guile project.
Re: Reader option to permit brackets as parentheses
- To: guile@cygnus.com
- Subject: Re: Reader option to permit brackets as parentheses
- From: Peter Chang <weasel@cs.stanford.edu>
- Date: Thu, 1 Jul 1999 20:05:06 -0700
- References: <377B0CB8.A473C0D1@ozemail.com.au>; from Chris Bitmead on Thu,Jul 01, 1999 at 04:37:45PM +1000<qrrr9mu4tw7.fsf@elwha.cs.washington.edu><3779AC8E.A5A1BA79@ozemail.com.au><qrraeth3c92.fsf@elwha.cs.washington.edu><377AC053.F3E9A1BB@ozemail.com.au><qrrzp1h2fvx.fsf@elwha.cs.washington.edu><199907010401.VAA21885@arathorn> <377B0CB8.A473C0D1@ozemail.com.au>
At 19:59 -0700 07.01.1999, Telford Tendys wrote:
>> Is that what python is? Sounds like a _very_ bad idea to have code
>> meaning depending on whitespace.
>
>Why? Whitespace is understandable, obvious, easy to edit, easy to align.
This comment causes flashbacks to when I was learning 'make'. I did not
realize that it was tab not just whitespace that was relevant. The error
message that make came back w/ wasn't really helpful to me at that point
either.
Anyway...
>I think that people had this big reaction against whitespace when
>they saw Pascal and C as the next big thing that would replace FORTRAN
>and they wanted to show that they were cool by allowing whitespace
>to be anywhere at all. Since then all they have done is argue over
>indentation and pretty printing standards...
If whitespace has semantics then isn't just enforcing indentation and
printing? Ofcourse, this is getting way off the track. Anyway, using a
'smart' editor makes most of the grouping/indenting problem a non-issue.
\p
---
sed quis custodiet ipsos custodes
--Juvenal *Satire* VI, 165