On Wed, 20 Apr 2005, Peter Dalgaard wrote:
Luke Tierney [EMAIL PROTECTED] writes:
Vectorized operations in R are also as fast as compiled C (because
that is what they are :-)). A compiler such as the one I'm working on
will be able to make most difference for non-vectorizable or not very
I hope to be making some substantial progress on this over summer.
But I would not hold up any projects in anticipation of major R
changes--the current recommended strategy of first writing something
that is correct, profiling to find out where a performance problem is
if there is one, and then
Dear Prof. Tierney,
Thank for very much for replying and we all appreciate what you have
done for the R community. Currently I have been spoiled by R. I would
love to be 100% R.
I talked to Andy Liaw yesterday about how to make R faster. Maybe we
need to explicitly declare variables in the
It is quite likely that we will move in a direction of supporting
annotations or declarations of some sort as well--at least that is one
of the things I am planning to investigate. I believe there is still
some room for improvement without this, but larger improvements will I
believe require some
Luke Tierney [EMAIL PROTECTED] writes:
Vectorized operations in R are also as fast as compiled C (because
that is what they are :-)). A compiler such as the one I'm working on
will be able to make most difference for non-vectorizable or not very
vectorizable code. It may also be able to
On Wed, 20 Apr 2005, Peter Dalgaard wrote:
Luke Tierney [EMAIL PROTECTED] writes:
Vectorized operations in R are also as fast as compiled C (because
that is what they are :-)). A compiler such as the one I'm working on
will be able to make most difference for non-vectorizable or not very
Do you mean the byte code compiler? You can find it at:
http://www.stat.uiowa.edu/~luke/R/compiler/
Andy
From: Jason Liao
I am excited to learn that Prof. Tierney is bringing to us compiled R.
I would like to learn when it will be available. This information will
be useful in scheduling
