[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Found problem with Subrs parsing...
From: |
Tom Kacvinsky |
Subject: |
Re: Found problem with Subrs parsing... |
Date: |
Mon, 24 Jul 2000 15:47:48 -0400 (EDT) |
Hi all,
>
> >The "offending" code is in z1load.c (function parse_subrs). I have
> >not yet thought of an elegant patch for this. David?
>
> I'll have a look, too.
>
I have been thinking about this. I am afraid that because there can
be gaps in the subrs (i.e., subrs 11 - 19 are missing) *and* the subrs
need not be in ascending order that the only way to do this is as
follows:
read a token, make sure it is not def (or expands to something ending
in def, like ND [= noaccess def]
if token expands to something ending in def, abort loop.
otherwise, read dup <index> RD ... NP, and add subr to subr table,
with appropriate error messaging.
loop
Sound about right?
Tom
- Found problem with Subrs parsing..., Tom Kacvinsky, 2000/07/24
- Re: Found problem with Subrs parsing..., Just van Rossum, 2000/07/24
- Re: Found problem with Subrs parsing...,
Tom Kacvinsky <=
- Re: Found problem with Subrs parsing..., Just van Rossum, 2000/07/25
- Re: Found problem with Subrs parsing..., Tom Kacvinsky, 2000/07/25
- Re: Found problem with Subrs parsing..., Just van Rossum, 2000/07/25
- Re: Found problem with Subrs parsing..., Tom Kacvinsky, 2000/07/25
- Re: Found problem with Subrs parsing..., Just van Rossum, 2000/07/25
- Re: Found problem with Subrs parsing..., David Turner, 2000/07/25
Re: Found problem with Subrs parsing..., Just van Rossum, 2000/07/25