ze
> the
> > > > > internal state to disk. I think this task was simply not considered
> > > > > in the
> > > > > design.
> > > > >
> > > > > Reason for writing to the mailing list are the troubles in
> connecting
>
t; > > >
> > > > It is not exceptionally heavy but also not very easy to serialize the
> > > > internal state to disk. I think this task was simply not considered
> > > > in the
> > > > design.
> > > >
> > > > Reas
I think this task was simply not considered
> > > in the
> > > design.
> > >
> > > Reason for writing to the mailing list are the troubles in connecting
> > > the
> > > TREE_CODE enumeration to the appropriate struct tree_node memory
> > > layout
>
ing
> > the
> > TREE_CODE enumeration to the appropriate struct tree_node memory
> > layout
> > without guessing.
> >
> > Can you provide a mapping of TREE_CODE to tree_node memory layout?
>
> I don't know that such a mapping exists directly, but have a
ink this task was simply not considered
> in the
> design.
>
> Reason for writing to the mailing list are the troubles in connecting
> the
> TREE_CODE enumeration to the appropriate struct tree_node memory
> layout
> without guessing.
>
> Can you provide a mapping of
this task was simply not considered in the
> design.
>
> Reason for writing to the mailing list are the troubles in connecting the
> TREE_CODE enumeration to the appropriate struct tree_node memory layout
> without guessing.
>
> Can you provide a mapping of TREE_CODE to tree_node memory
g the
TREE_CODE enumeration to the appropriate struct tree_node memory layout
without guessing.
Can you provide a mapping of TREE_CODE to tree_node memory layout?
kind regards
