[
https://issues.apache.org/jira/browse/ETCH-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642720#comment-13642720
]
Sebastian Setzer commented on ETCH-271:
---------------------------------------
Im not sure if doing a deep copy is the right fix, or if it should be solved by
the the reference counter. I don't understand the rereference counting
mechanism of etch, yet. I just saw that there is a refcount member in
etch_object. Didn't find design documentation on that issue.
> clone does no deep copy, but destroy destroys deeply
> ----------------------------------------------------
>
> Key: ETCH-271
> URL: https://issues.apache.org/jira/browse/ETCH-271
> Project: Etch
> Issue Type: Bug
> Components: binding-c
> Affects Versions: 1.2
> Environment: all
> Reporter: Sebastian Setzer
> Priority: Blocker
>
> In etch_arraylist, clone does no deep copy. Martin has a hotfix for that -
> but it doesn't solve all problems.
> We still get invalid values in a clone, after destroying the original (Only
> the crashes are gone).
> I assume that's because the generated clone methods also don't do a deep copy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
