33 lines
1.3 KiB
Plaintext
33 lines
1.3 KiB
Plaintext
From: neelk at brick.cswv.com (Neel Krishnaswami)
|
|
Date: 28 Apr 1999 19:34:24 -0500
|
|
Subject: Python IS slow ! [was] Re: Python too slow for real world
|
|
References: <613145F79272D211914B0020AFF6401914DAD8@gandalf.digicool.com> <p5g15lmb35.fsf@bidra241.bbn.hp.com> <slrn7ieipq.8uk.wtanksle@dolphin.openprojects.net> <372769B0.3CE8C0F3@prescod.net>
|
|
Message-ID: <7g89eg$vb0$1@brick.cswv.com>
|
|
X-UID: 975
|
|
|
|
In article <372769B0.3CE8C0F3 at prescod.net>,
|
|
Paul Prescod <paul at prescod.net> wrote:
|
|
>William Tanksley wrote:
|
|
>>
|
|
>> And Oberon (SlimBinaries), and Eiffel (typing and general compile-time
|
|
>> error catching), and ...
|
|
>
|
|
>Actually, isn't Eiffel's type system famous for being full of holes?
|
|
>
|
|
>Regardless, wouldn't a better source of inspiration on typing be a
|
|
>language with *optional* compile-time error checking?
|
|
|
|
I've been playing around with Dylan recently, and it seems like what
|
|
Python would be if you added "end" blocks and mated it with CLOS. Since
|
|
Dylan is nearly as dynamic as Python, I think it might be a good source
|
|
of inspiration for Python 2. (And it might even be the case that the
|
|
Dylan-to-C compiler might be a source of good bits to improve Python's
|
|
speed. I haven't looked at the source yet, though.)
|
|
|
|
|
|
Neel
|
|
|
|
|
|
|
|
|