Hello Gerrit,
the attempt to move ref counting into fields is getting closer to
completion, but some loose strings remain:
- DynamicFieldAttachment makes use of FieldDescription::createField to
create the instance of the field to add. This has the assumption that
fields are default constructible, which is not true anymore for
{S|M}ChildFCPointerField, which takes a pointer to the enclosing
container, its field id in that container and the id of the field that
stores the corresponding parent pointer as arguments.
This leads to a couple of questions:
- Do we want to support child/parent linking with fields added to a
DynamicFieldAttachment ?
- Should the child pointer field be default constructible but
inoperable in that case ?
- Other ideas ?
- The VRML loader is currently disabled in my tree as it has some unique
uses of FieldDescriptions. I have not yet looked into how to fix it, but
it seems less trivial than all the other places. Since there has been
more than one VRML loader floating around, is the one in trunk the one
that will be used in 2 ?
- Can you give me a high level description of how it operates ? That
would help me a lot understanding it.
Thanks,
Carsten
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
