John Tobey <[EMAIL PROTECTED]> writes: >Dan Sugalski <[EMAIL PROTECTED]> wrote: >> Yup, and I realized one of my big problems to GCs that move memory >> (references that are pointers and such) really isn't, if we keep the >> two-level variable structure that we have now. The 'main' SV structure >> won't move, while the guts that the equivalent of sv_any points to can >> without a problem. > >I certainly hope this data layout factoid is still subject to change. Having an SV have a fixed address is handy for C extensions. The 'entity' has got to have some 'handle' to defines its existance. If not the SV* data structure then what is it that defines the thing? -- Nick Ing-Simmons
- perl6-internals-gc sublist John Tobey
- Re: perl6-internals-gc sublist John Tobey
- Re: perl6-internals-gc sublist Dan Sugalski
- Re: perl6-internals-gc sublist Chaim Frenkel
- Re: perl6-internals-gc sublist Dan Sugalski
- Re: perl6-internals-gc sublist John Tobey
- Re: perl6-internals-gc sublist Dan Sugalski
- Re: perl6-internals-gc sublist Nick Ing-Simmons
- Re: perl6-internals-gc subl... John Tobey
- Re: RFC 35 / Re: perl6-inte... Nick Ing-Simmons
- Re: RFC 35 / Re: perl6-inte... Dan Sugalski
- Re: RFC 35 / Re: perl6-inte... Chaim Frenkel
- Re: RFC 35 / Re: perl6-inte... Dan Sugalski
- Re: RFC 35 / Re: perl6-inte... Chaim Frenkel
- Re: RFC 35 / Re: perl6-inte... John Tobey
- Re: RFC 35 / Re: perl6-inte... John Tobey
- Re: RFC 35 / Re: perl6-inte... Dan Sugalski
- Re: RFC 35 / Re: perl6-inte... Ken Fox