Follow-up Comment #3, bug #25266 (project gnustep):
With re-work I just meant that my current bug fixing approach to the problem
may not be sufficient, but perhaps I just gave up one patch too early?
You see, I am very sure that both my patches are correct, but currently
things get worse when applying them. So perhaps to whole concept in this file
is wrong.
What we need to do here, as far as I understand it is
- Code complex NIB files correctly
- Allow for the process to replace objects while instantiating them (Normally
via awakeFromNib)
- Don't leak any memory.
The current implemantion does great on the first two items, it falls short on
the third one. This may well be because the second should be implemented
differently. But this is hard to tell without an outlined concept for the
current implementation. Either that concept could be wrong or just the
implementation.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25266>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep
