From: Joseph W. <jo...@gn...> - 2006-09-24 04:25:48
|
The R backend seem to have broke with the new tree.c. The problem seems to be that when tree.c was using raw strings, that it would create a new object when putting in a hash key, but when it is passing in object it does just a pointer copy. This causes badness when (as is the case) the string object is a temporary object that is later modified. I got it to work by passing Char(temp) to Setattr instead of temp. I can check in the changes if no one objects. Also, I seem to be having problems posting onto the swig-devel list. I've unsubed and subed and hopefully that should help. |
From: Olly B. <ol...@su...> - 2006-09-24 04:29:28
|
On Sat, Sep 23, 2006 at 11:25:36PM -0500, Joseph Wang wrote: > The R backend seem to have broke with the new tree.c. The problem seems to be > that when tree.c was using raw strings, that it would create a new object > when putting in a hash key, but when it is passing in object it does just a > pointer copy. This causes badness when (as is the case) the string object is > a temporary object that is later modified. Sorry about that - I'd already noticed the problem myself and checked in a fix about half an hour ago. If you're still see problems with the latest CVS HEAD, let me know. Cheers, Olly |