Nicholas Clark wrote:
The summary reminded me I had a question still
On Thu, Jan 30, 2003 at 08:42:34AM +0100, Leopold Toetsch wrote:
[ constant folding for eval ]
Create a hash table of values present at the time of the first eval, and
use that from then on?
There are 2 possibilities:
The summary reminded me I had a question still
On Thu, Jan 30, 2003 at 08:42:34AM +0100, Leopold Toetsch wrote:
> Nicholas Clark wrote:
> >If I understand you correctly, every time an eval happens, more code is
> >created, and that code's associated constants are appended to the constant
> >table
Nicholas Clark wrote:
On Wed, Jan 29, 2003 at 02:12:01PM +0100, Leopold Toetsch wrote:
The variable layout of interpreter->code (actually the packfile) doesn't
fit very good for multiple code segments. There is only one ->byte_code
pointer, the byte_code_size is in bytes and converted zig tim
On Wed, Jan 29, 2003 at 02:12:01PM +0100, Leopold Toetsch wrote:
> The variable layout of interpreter->code (actually the packfile) doesn't
> fit very good for multiple code segments. There is only one ->byte_code
> pointer, the byte_code_size is in bytes and converted zig times into
> opcode_t'
The variable layout of interpreter->code (actually the packfile) doesn't
fit very good for multiple code segments. There is only one ->byte_code
pointer, the byte_code_size is in bytes and converted zig times into
opcode_t's and so on.
so:
1) rename interpreter->code to interpreter->pf (the pa
