<br><br><div class="gmail_quote">On Mon, Jan 10, 2011 at 12:02 PM, 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 class="im"><br>
On 10 January 2011 at 11:36, Dominick Samperi wrote:<br>
|<br>
|<br>
| On Mon, Jan 10, 2011 at 11:09 AM, Dirk Eddelbuettel <<a href="mailto:edd@debian.org">edd@debian.org</a>> wrote:<br>
|<br>
|<br>
| On 10 January 2011 at 11:04, Dominick Samperi wrote:<br>
| | On Mon, Jan 10, 2011 at 10:32 AM, Dirk Eddelbuettel <<a href="mailto:edd@debian.org">edd@debian.org</a>><br>
| wrote:<br>
| | We (somewhat breathlessly) await your patches.<br>
| |<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>
| Just let us know the URL of your carefully tested patch.<br>
|<br>
|<br>
| It is not my responsibility to fix your memory bugs. I have<br>
| contributed the solution. How and when you implement it<br>
| is up to you, and apps that depend on Rcpp may crash<br>
| unpredictably until you do.<br>
<br>
</div>Nonsense. You are just like a crank standing on a soap box in Hyde Park,<br>
proclaiming the end of the universe.<br></blockquote><div> </div><div>Exactly what part of this is nonsense? Is the memory corruption that was<br>observed by Doug, me, and you an optical illusion? Is the fix that I proposed<br>
and that was confirmed by the three of us a dream?<br><br>In the process of tracking down this bug I learned quite a bit about<br>what Romain has added to Rcpp, and admire his creativity. It is too bad<br>that he had to team up with somebody who is more politician than<br>
software developer, somebody who does not see the absurdity of<br>insulting somebody who contributes a fix for a serious memory bug<br>instead of showing some appreciation, and somebody who actually<br>tries to make excuses for an obvious memory bug instead of<br>
fixing it.<br><br>For those Rcpp users who may have doubts, turn on garbage collection<br>after every allocation by running gctorture() before running the<br>functions of your package (assuming that your package depends<br>
on Rcpp, of course). It is highly likely that your functions will<br>fail. They will also run very slowly. If your functions seem to work<br>without gctorture() that is because you are lucky. There is<br>no guarantee that a garbage collection will not invalidate one or<br>
more objects that your program depends on.<br><br>If you perform this test please feel free to report your results on<br>this mailing list.<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;">
<br>
You have contributed nothing of value here. I already debunked your<br>
so-called fix once before. By endlessly repeating the same claims, you are<br></blockquote><div><br>Just to refresh your memory, the reason we parted ways years ago is<br>that it became apparent to me that you didn't have much to contribute, and that<br>
you tended to release software that was untested and buggy (sometimes<br>with my name attached). Now you are free-riding on the efforts of<br>Romain, and I suspect that he has similar reservations about your<br>dismissive attitude regarding quality control and reliability (because he<br>
is obviously a very talented software developer).<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;">
not enhancing your position. Neither does leaving your one package on CRAN<br>
in its will-not-even-compile state [1]. How much credibility does that give<br>
you, exactly?<br></blockquote><div> </div><div>My package cxxPack does not compile because YOU "released"<br>
RcppClassic, work that is 99% due to me, as "deprecated," for the benefit of a<br>
user community that does not exist, without checking with me or<br>
doing any kind of integration testing (apparently an alien concept<br>
for you). Releasing this (deprecated!) package makes no sense <br>given the existence of the current version of Rcpp, and was done<br>for reasons that have nothing to do with software quality. <br><br>Need I remind you that I had to submit bug reports to fix <br>
Date problems in Rcpp, problems that did not exist in the<br>"deprecated" software from which this Date functionality<br>stemmed?<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;">
<br>
Please put up (patches are welcome), or shut up.<br></blockquote><div><br>You are contradicting your remark above that you have "debunked"<br>my so-called fix. Why then would patches be needed?<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;">
<br>
Dirk<br>
<br>
[1] <a href="http://cran.r-project.org/web/checks/check_results_cxxPack.html" target="_blank">http://cran.r-project.org/web/checks/check_results_cxxPack.html</a><br>
<font color="#888888"><br>
--<br>
</font><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>