9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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: Sat,  3 May 2008 19:50:40 -0400	[thread overview]
Message-ID: <EEAC02E8-458D-4B19-B87D-A6AAC4F8FEEE@mac.com> (raw)
In-Reply-To: <775b8d190805031632k1b6d5f50l7e44a9f13dabe7f6@mail.gmail.com>

We have two ratpies. They're ruby and perl. Pick your poison.

On May 3, 2008, at 7:32 PM, Bruce Ellis wrote:

> ratpie! tasty. i thought a pindent was what a pinhead gets when you
> scone him with a frypan.
>
> brucee
>
> On Sun, May 4, 2008 at 9:28 AM, Skip Tavakkolian <9nut@9netics.com>
> wrote:
>> my original suggestion for ratpy wasn't taken seriously, so i'll
>> propose it again:
>>
>> http://groups.google.com/group/comp.os.plan9/msg/29eb245edcb78e91
>>
>>>>> I don't use Python for this very reason.  This is probably why
>>>>> Ruby exists.  I will not use your language for the same reason.
>>>>> By adopting such draconian white space rules you automatically
>>>>> alienate a large number of programmers.
>>>>
>>>> A blind programmer once told me that Python's whitespace block
>>>> structure was simply too high of a barrier for him to use it.
>>>
>>> straying off-topic, but ...
>>>
>>> the Python distribution includes a tool called 'pindent'.  it
>>> happily
>>> annotates Python source with block-closing comments and converts
>>> haphazardly indented source with block-closing comments into
>>> correctly indented Python source.
>>>
>>>    http://svn.python.org/projects/python/trunk/Tools/scripts/pindent.py
>>
>>
>>
>




  reply	other threads:[~2008-05-03 23:50 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
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 [this message]
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=EEAC02E8-458D-4B19-B87D-A6AAC4F8FEEE@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).