Recommended packages cluster codetools foreign lattice nlme and rpart
have tests, for example. (As do standard packages grDevices, grid and
stats.)
On Mon, 31 Mar 2008, Christophe Genolini wrote:
>
>>
>> Generally I find it's good to look at examples that work. For
>> examples of packages usin
>
> Generally I find it's good to look at examples that work. For
> examples of packages using tests, look at source packages on CRAN.
> Run the tests on them (using R CMD check), and see what gets produced.
>
Do you have the name of a package that use it ? I try the 10 first
package, and 10
Hi the devel list.
I am adapting the package.skeleton to S4 classes and methods
I would have been very proud to post a new working function on this list.
Unfortunately, I do not manage to solve all the problems. Mainly
- sys.source does not compile a file with setClass
- dumpMethod does not exi
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Kyeongmi Cheon
> Sent: Saturday, March 29, 2008 9:09 PM
> To: r-devel@r-project.org
> Subject: [Rd] norm_rand() in R-extension vs rnorm in R ---which is better?
>
> I need to generate good quality of ra
Full_Name: Simon Anders
Version: 2.6.2
OS: Ubuntu Linux
Submission from: (NULL) (86.22.75.91)
This is a rather minor "documentation bug", certainly not at all urgent.
The manual "Writing R extensions" explains in section 5.10 ("Evaluating R
expressions from C") how to use the eval function. Wit
Thanks. So its intended to jump straight out of deeply nested
calls without having to manage the unwinding.
On Sun, Mar 30, 2008 at 4:22 PM, Luke Tierney <[EMAIL PROTECTED]> wrote:
> On Sun, 30 Mar 2008, Gabor Grothendieck wrote:
>
> > Sorry it should be as follows:
> >
> > fib <- function(i, a =
On Sun, 30 Mar 2008, Gabor Grothendieck wrote:
> Sorry it should be as follows:
>
> fib <- function(i, a = 0, b = 1) {
> if (i == 0) b else fib(i-1, b, a+b)
> }
>
> Now, how do we transform that to use callCC?
>
>
> On Sun, Mar 30, 2008 at 1:42 PM, Gabor Grothendieck
> <[EMAIL PROTECTED]> wrote:
OK. Can you show code to implement the tail recursive version of
fib using callCC in R, say.
Here it is transformed to tail recursive style:
fib <- function(i, a = 0, b = 1) {
if (i == 0) a else fib(i-1, b, a+b)
Now, how do I add callCC to all this so that the fib call
presumably does not crea
On Sun, 30 Mar 2008, Gabor Grothendieck wrote:
> I think the only relationship to that is the name since
> it does not appear to allow one to leave a function
> in the middle of its processing and re-enter it back
> at that point -- which is what would be needed.
The article conflates basic CPS w
I came across this in googling for continuations and was surprised when
I found it in R 2.7.0 and since I had not come across it before I assumed
it was added just now.
Can you explain how its intended to be used with an example
that is more realistic than in the example section.
On Sun, Mar 30,
Sorry it should be as follows:
fib <- function(i, a = 0, b = 1) {
if (i == 0) b else fib(i-1, b, a+b)
}
Now, how do we transform that to use callCC?
On Sun, Mar 30, 2008 at 1:42 PM, Gabor Grothendieck
<[EMAIL PROTECTED]> wrote:
> OK. Can you show code to implement the tail recursive version o
On Sun, 30 Mar 2008, Gabor Grothendieck wrote:
> Also in trying it out again it seems that its not like
> on.exit but more like return:
Yes -- if you can point out what in the documentation ever gave the
idea it might be like on.exit then we can fix the documentation.
>
> F <- function(f) { f(10
Also in trying it out again it seems that its not like
on.exit but more like return:
F <- function(f) { f(10); print(2); f(20); 3}
callCC(F)
acts the same as:
F <- function() { return(10); print(2); f(20); 3}
F()
and there is no documented way to restart F
at the point it left off so I assume i
I think the only relationship to that is the name since
it does not appear to allow one to leave a function
in the middle of its processing and re-enter it back
at that point -- which is what would be needed.
On Sun, Mar 30, 2008 at 12:04 PM, <[EMAIL PROTECTED]> wrote:
>
> > Would anyone like to
> Would anyone like to explain if callCC in R 2.7.0 gives
> anything that on.exit does not already provide?
>
> It seems that the exit condition once defined cannot
> be added to overridden whereas with on.exit multiple
> on.exit's add additional on.exits rather than being ignored.
>
> Is this impo
Would anyone like to explain if callCC in R 2.7.0 gives
anything that on.exit does not already provide?
It seems that the exit condition once defined cannot
be added to overridden whereas with on.exit multiple
on.exit's add additional on.exits rather than being ignored.
Is this important?
__
On Sun, Mar 30, 2008 at 5:52 AM, Jean lobry
<[EMAIL PROTECTED]> wrote:
> Dear all,
>
> I'm confused by the time serie parameters in data(lh) :
>
> sueoka:~ lobry$ R --vanilla --quiet
> > tsp(lh)
> [1] 1 48 1
>
> because documentation says:
>
> QUOTE
> A regular time series giving the luteinizing
Dear all,
I'm confused by the time serie parameters in data(lh) :
sueoka:~ lobry$ R --vanilla --quiet
> tsp(lh)
[1] 1 48 1
because documentation says:
QUOTE
A regular time series giving the luteinizing hormone in blood
samples at 10 mins intervals from a human female, 48 samples.
UNQUOTE
So
18 matches
Mail list logo
