Unfortunately a claim of 'extensive regression testing' is not going to
help you if the original contains the mistake. It seems that your package
is not using these functions as they are (and always have been, AFAIK)
documented in R or the Blue and White Books.
A summary would be that new che
The number of packages on CRAN usable with the current version of R is
recorded from time to time in the file tests/internet.Rout.save. So e.g.
on 2001-05-30 there were 106 and on 2004-12-27 there were 433 (rather less
than you recorded) and on 2005-12-17, 647 (rather more), assuming I got
the
Hi,
I was just looking at the "CRAN Daily Package Check Results"
[http://cran.r-project.org/src/contrib/checkSummary.html], and
realized there are 1000 packages on CRAN as of today (look at row 3 in
the table below). Yet another quite extraordinary milestone in R
history.
Last updated on 2007-04
On Thu, 12 Apr 2007, mel wrote:
Prof Brian Ripley a écrit :
If you are using Rgui (it should work under rterm)
yes indeed, it works under rterm
there is no C-level 'stdout' file stream (the normal state
for Windows GUI programs), so no way to capture it inside R.
Aie ! (I feared this ans
Prof Brian Ripley a écrit :
> If you are using Rgui (it should work under rterm)
yes indeed, it works under rterm
> there is no C-level 'stdout' file stream (the normal state
> for Windows GUI programs), so no way to capture it inside R.
Aie ! (I feared this answer). Thanks however for the exp
> On Thu, 12 Apr 2007 07:35:28 -0500 (CDT),
> Luke Tierney (LT) wrote:
> On Thu, 12 Apr 2007, Friedrich Leisch wrote:
>>> On Wed, 11 Apr 2007 17:28:31 -0500 (CDT),
>>> Luke Tierney (LT) wrote:
>>
>> > It would appear that printing the error message to stderr() is what is
On Thu, 12 Apr 2007, Friedrich Leisch wrote:
>> On Wed, 11 Apr 2007 17:28:31 -0500 (CDT),
>> Luke Tierney (LT) wrote:
>
> > It would appear that printing the error message to stderr() is what is
> > causing the build to fail; replace
>
> >try(stop('err'))
>
> > with
>
> >cat('
Prof Brian Ripley wrote:
> If you are using Rgui (it should work under rterm) there is no C-level
> 'stdout' file stream (the normal state for Windows GUI programs), so no
> way to capture it inside R.
>
> On Thu, 12 Apr 2007, mel wrote:
>
>
>> printf capture
>>
>> Dear All,
>>
>> I'm running
> On Wed, 11 Apr 2007 17:28:31 -0500 (CDT),
> Luke Tierney (LT) wrote:
> It would appear that printing the error message to stderr() is what is
> causing the build to fail; replace
> try(stop('err'))
> with
> cat('Error in try(stop("err")) : err\n', file = stderr())
> On Sat, 07 Apr 2007 07:56:40 -0400,
> Roger Peng (RP) wrote:
> [I originally emailed this to Friedrich Leisch but got no response
Sorry, was on easter vacation and have not fully suceeded to go through
all mails in my inbox yet.
> and I
> just wanted to make sure it made it in b
If you are using Rgui (it should work under rterm) there is no C-level
'stdout' file stream (the normal state for Windows GUI programs), so no
way to capture it inside R.
On Thu, 12 Apr 2007, mel wrote:
> printf capture
>
> Dear All,
>
> I'm running R-2.4.1 on WindowsXP.
> I wrote a small C++ D
printf capture
Dear All,
I'm running R-2.4.1 on WindowsXP.
I wrote a small C++ DLL using Rprintf() and all works fine
dyn.load(), is.loaded('f1'), Rprintf(), .C(), all is ok.
Now, the worry :
I use also a 3rd party piece of C++ program which was not designed
for R and uses printf().
I though on
Gregor Gorjanc wrote:
> I have recently found RForge.net (http://www.rforge.net/) by Simon
> Urbanek and found out today that the site is accepting subscriptions.
> Great! However, browsing a bit on the site I found a link to another
> forge: R-Forge (http://r-forge.r-project.org/).
>
> Is/will t
13 matches
Mail list logo
