"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Certainly, "(almost) everything is an object" is a good start. Are
> there any other axiom like statements one can hang their hat on when
> trying to wrap their brain around Python's architecture?
As John Nagle put it, the data store is a tree of
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> I'm learning Scheme and I am amazed how easy it is to start building a
> half baked Scheme implementation that somewhat works.
>
> After knowing Python for *years* I have no idea how to actually
> implement the darn thing.
Since you know Scheme, pe
On 21 Feb., 18:28, John Nagle <[EMAIL PROTECTED]> wrote:
> The run-time data implementation is all dictionaries. In Python,
> everything is a variable-sized hash. You don't even have to allocate
> storage during compile time. The run-time environment is a tree of hashes.
Except that it is
On 21 Feb, 18:28, John Nagle <[EMAIL PROTECTED]> wrote:
>
> Why? It's not very difficult. Get a parser for LALR(1) grammars,
> like YACC or Bison, write a tokenizer that understands Python indentation,
> hook up a dictionary, and parse the thing into a tree. This is all
> covered in Compile
[EMAIL PROTECTED] wrote:
> I'm learning Scheme and I am amazed how easy it is to start building a
> half baked Scheme implementation that somewhat works.
>
> After knowing Python for *years* I have no idea how to actually
> implement the darn thing.
Why? It's not very difficult. Get a pars
On Feb 19, 2008 3:15 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Does this have to be true? Beneath the more complex syntax are there
> a few core design principles/objects/relationships to help in grokking
> the whole thing? Got any related links?
Take a look at a simpler implementation,
On Feb 19, 11:22 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> On Feb 19, 9:49 pm, Kay Schluehr <[EMAIL PROTECTED]> wrote:
>
> > Building a
> > Python VM in a high level language is certainly not harder than
> > creating a Scheme interpreter.
>
> Does VM = interpreter?
> Are you saying imple
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Does VM = interpreter?
I think it means the bytecode interpreter.
--
http://mail.python.org/mailman/listinfo/python-list
On Feb 19, 9:49 pm, Kay Schluehr <[EMAIL PROTECTED]> wrote:
> Building a
> Python VM in a high level language is certainly not harder than
> creating a Scheme interpreter.
Does VM = interpreter?
Are you saying implementing a toy Python interpreter is not any harder
than implementing a toy Scheme i
On 19 Feb., 07:15, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Certainly, "(almost) everything is an object" is a good start. Are
> there any other axiom like statements one can hang their hat on when
> trying to wrap their brain around Python's architecture?
>
> Chris
It's a natural way to
On Feb 19, 7:15 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> I'm learning Scheme and I am amazed how easy it is to start building a
> half baked Scheme implementation that somewhat works.
This was true for R5RS Scheme, not anymore.
Michele Simionato
--
http://mail.python.org/mailman/l
http://codespeak.net/pypy/dist/pypy/doc/getting-started.html#what-is-...
>
> George
I'm very excited about PyPy. It would still be nice to see a
nice succinct list of major design principles of Python
implementations somewhere.
chris
--
http://mail.python.org/mailman/listinfo/python-list
On Feb 19, 1:15 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> I'm learning Scheme and I am amazed how easy it is to start building a
> half baked Scheme implementation that somewhat works.
>
> After knowing Python for *years* I have no idea how to actually
> implement the darn thing.
>From
I'm learning Scheme and I am amazed how easy it is to start building a
half baked Scheme implementation that somewhat works.
After knowing Python for *years* I have no idea how to actually
implement the darn thing.
Does this have to be true? Beneath the more complex syntax are there
a few core d
14 matches
Mail list logo
