<br><br><div class="gmail_quote">On Mon, Jan 10, 2011 at 10:32 AM, Dirk Eddelbuettel <span dir="ltr"><<a href="mailto:edd@debian.org">edd@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5"><br>
On 10 January 2011 at 10:10, Dominick Samperi wrote:<br>
|<br>
|<br>
| On Sun, Jan 9, 2011 at 1:52 PM, Dirk Eddelbuettel <<a href="mailto:edd@debian.org">edd@debian.org</a>> wrote:<br>
|<br>
|<br>
| On 9 January 2011 at 12:41, Douglas Bates wrote:<br>
| | I'm sorry to say that I will need to abandon the debugging of this.<br>
| |<br>
| | I have converted the code in Rcpp/R/exceptions.R to using a R<br>
| | functions with a common environment to keep track of the error<br>
| | conditions. I can get access to those from within the C++ code<br>
| | through values established during the execution of R_init_Rcpp but the<br>
| | next time I try to use them in the C++ code they are gone, although<br>
| | they are still there are the R side. It is bizarre - I have no idea<br>
| | what is going on.<br>
| |<br>
| | Anyway, I need to turn my attention back to lme4a. I am giving a<br>
| | short course starting tomorrow and must have a version of lme4a that<br>
| | can compile and run. I have been converting it to use Rcpp Modules<br>
| | and it looks like I will need to strip all that code out. I hope that<br>
| | the problems with memory protection are isolated in the Modules<br>
| | sections of Rcpp.<br>
|<br>
| Thanks for all your help on modules.<br>
|<br>
| You have been pushing this harder and further than anybody else, and it is<br>
| too bad that it turned out to be inapplicable for your use case, at least<br>
| in<br>
| the current state of affairs.<br>
|<br>
| Modules work for my use case. I may upload the wrapping of Boost Date_Time<br>
| to<br>
| CRAN one of these days. Should write some more documentation though.<br>
| Writing that small package was a rather pleasant experience.<br>
|<br>
|<br>
| It seems to me that memory corruption issues are not a matter of "use case"<br>
| and fixing them should be given the highest priority. Am I missing something<br>
| here?<br>
<br>
</div></div>We (somewhat breathlessly) await your patches.<br></blockquote><div><br>I already submitted a clear explanation of how to fix the problem earlier<br>in this thread, with examples. This involved a lot of work. The fix is<br>
straightforward (if tedious), and without this fix SEXP's will be<br>unpredictably blown away, leading to a crash.<br><br>Dominick<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<font color="#888888"><br>
Dirk<br>
</font><div class="im"><br>
| In case anybody wants to look at that, it is on R-Forge inside the Rcpp<br>
| repo.<br>
|<br>
| Dirk<br>
|<br>
| --<br>
| Dirk Eddelbuettel | <a href="mailto:edd@debian.org">edd@debian.org</a> | <a href="http://dirk.eddelbuettel.com" target="_blank">http://dirk.eddelbuettel.com</a><br>
|<br>
|<br>
<br>
</div>--<br>
<div><div></div><div class="h5">Dirk Eddelbuettel | <a href="mailto:edd@debian.org">edd@debian.org</a> | <a href="http://dirk.eddelbuettel.com" target="_blank">http://dirk.eddelbuettel.com</a><br>
</div></div></blockquote></div><br>