Thanks,
not much need for convincing here, just wanted a big enough push to get me
over that 'kinda works so why bother` hurdle.
I need to do other code refactoring in Gviz soon, and will take the
opportunity to kick out all initialisers in the process. So one less
package to worry about.
Florian
In the S4Vectors/IRanges infrastructure, we have never defined an
initialize method, so it is certainly possible to use the constructor
pattern in complex frameworks, and IRanges serves as a good example of
doing so. The basic pattern is to delegate to the superclass
constructor and pass that
Hi Dan,
Now I have included source code of the rsampl.h in the GOAL package.
Although, rlecuyer is good candidate for random number generator, I
currently avoid using it because I wanted results of our submitted
manuscript to be completely reproducible. I can reproduce the results using
ransampl
I might add that the old (very old) style in Biobase was to use new as
constructor. That one should avoid this all the time, is a newer insight,
so you'll find plenty of old code violating this.
Kasper
On Mon, Jan 26, 2015 at 8:35 AM, Hahne, Florian florian.ha...@novartis.com
wrote:
Thanks,
My favorite solution to this would be to use Rcpp attributes to add R-level
functions for each C function. You can use these just for testing and skip the
exporting and manual pages. That's not quite what you asked for but it would
work.
BTW transcription factors are my thing so I'm eager to
- Original Message -
From: Elena Grassi grass...@gmail.com
To: bioc-devel@r-project.org
Sent: Monday, January 26, 2015 1:14:59 AM
Subject: [Bioc-devel] unit tests for C code inside a package
Hi,
I'm writing a package that calculates total affinity (see PMID
21335606 and
Dear All,
We have planed to use R as our back-end for our c++ application using qt and
qtcreator. In order to connect it with R, we considered for using Rinside and
Rcpp as our connector. (RinsideRcpp are developed by Dirk Eddelbuettel).
Even though we succeed running the project under linux,
Hi Michael,
I'll take a look. In order to improve my code: what exactly do you think
should be part of the initialiser, and what should be in the constructor?
There don't seem to bee any clear guidelines out there anywhere. And if
all logic goes in the constructor, how does one deal with more
Hi,
I'm writing a package that calculates total affinity (see PMID
21335606 and 16873464 if transcription factors are your thing):
up until now in our lab we've used a pure C tool that needs fasta and
tabular formatted PFM-PWM files but we are willing to produce
something more comfortable that
