In article <[EMAIL PROTECTED]>,
gangesmaster <[EMAIL PROTECTED]> wrote:
>
>the following (random) code crashes my interpreter
>(python 2.4.3/winxp):
>
>from types import CodeType as code
>exec code(0, 5, 8, 0, "hello moshe", (), (), (), "", "", 0, "")
>
>i would expect the interpreter to do some ve
sam wrote:
> Mel:
> Wow that book brings back memories. I scanned my copy to review the
> subject covered, and came to the conclusion that mind reading
> algorithms are the answer.
>
I gathered from somewhere (but not the index to Andrew
Hodges' biography) that Turing was toying with an idea for
Mel:
Wow that book brings back memories. I scanned my copy to review the
subject covered, and came to the conclusion that mind reading
algorithms are the answer.
Sam Schulenburg
Mel Wilson wrote:
> sam wrote:
> > tomer:
> >
> > It is my opinion that you would loose performance if the Python
> > i
sam wrote:
> tomer:
>
> It is my opinion that you would loose performance if the Python
> interpreter had the additional task of verifying byte code. It might be
> more appropriate to have a preprocessor that did the verifying as it
> compiled the byte code.
Possibly. A good book on the topic is
sam <[EMAIL PROTECTED]> wrote:
> tomer:
>
> It is my opinion that you would loose performance if the Python
> interpreter had the additional task of verifying byte code. It might be
> more appropriate to have a preprocessor that did the verifying as it
> compiled the byte code.
But in this case,
tomer:
It is my opinion that you would loose performance if the Python
interpreter had the additional task of verifying byte code. It might be
more appropriate to have a preprocessor that did the verifying as it
compiled the byte code.
Sam Schulenburg
gangesmaster wrote:
> the following (random)
the following (random) code crashes my interpreter
(python 2.4.3/winxp):
from types import CodeType as code
exec code(0, 5, 8, 0, "hello moshe", (), (), (), "", "", 0, "")
i would expect the interpreter to do some verifying, at least for
sanity (valid opcodes, correct stack size, etc.) before exe
