From: Laura Creighton <lac@strakt.com>
To: 9fans@cse.psu.edu
Subject: [9fans] some of you guys clearly need something else to think about.
Date: Tue, 7 Oct 2003 16:38:22 +0200 [thread overview]
Message-ID: <200310071438.h97EcMcc015212@ratthing-b246.strakt.com> (raw)
I'll post my problem here. It's off topic, but not as there-and-hell-and-gone
as a lot of the off topic posts here.
I am trying to get the EU to fund my Python-In-Python Project. You can read
all about it at http://www.codespeak.net/pypy We're going to do this
anyway, but it would be nice to get this done for real in a stretch, rather
than on our vacations like we are doing now, even if we get 6 weeks a year
unlike you poor Americans with 2.
But JIT is not new. Smalltalk did it, and then self did it. We are way more
flexible, do type inference (only since last week!!! it works!!!) And we
can redo our high level analysis on execution. We will (don't yet) refactor
the generated code while interpreting the actual application. This might
be thought as "just in time program analysis". Somebody got a sexy word
to use to describe us? We need to say 'more than just a JIT' but we aren't
so hot with words.
Ideas? This has got to be more fun than picking fights with Jim Choate ...
Laura
next reply other threads:[~2003-10-07 14:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 14:38 Laura Creighton [this message]
2003-10-07 14:58 ` Nigel Roles
2003-10-07 16:48 ` matt
2003-10-07 17:05 ` matt
2003-10-07 15:13 ` Scott Schwartz
2003-10-07 15:16 ` Dan Cross
2003-10-07 15:23 ` Scott Schwartz
2003-10-07 15:46 ` Wes Kussmaul
2003-10-07 16:56 ` matt
2003-10-07 22:45 ` boyd
2003-10-08 3:49 ` Micah Stetson
2003-10-07 16:01 ` Rob Pike
2003-10-07 19:31 ` Charles Forsyth
2003-10-07 20:31 ` rob pike, esq.
2003-10-07 22:42 ` boyd
2003-10-07 23:13 ` Wes Kussmaul
2003-10-07 15:50 Richard C Bilson
2003-10-07 16:09 ` Wes Kussmaul
2003-10-07 23:34 jmk
2003-10-07 23:45 ` boyd
2003-10-08 2:18 ` okamoto
2003-10-08 0:15 ` boyd
2003-10-08 0:26 ` rob pike, esq.
2003-10-08 4:46 Skip Tavakkolian
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=200310071438.h97EcMcc015212@ratthing-b246.strakt.com \
--to=lac@strakt.com \
--cc=9fans@cse.psu.edu \
/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).