why not resolve field in constant pool?
gback at cs.utah.edu
Fri Oct 27 08:10:47 PDT 2000
> when kaffe resolves CONSTANT_Class in constant pool, it replaces it
> with CONSTANT_ResolvedClass, and records the pointer to class struct
> at constants.data[idx]. Why not treat field in the same way?
I don't think there's a particular reason.
I think you could do it, which means compiling PUT/GET FIELD/STATIC would
go a tad faster, but he'd have to allocate memory for the field infos
(and worry about freeing it later.)
More information about the kaffe