Dear all,
I haven't been working with R before, but has been asked by my
colleagues to investigate the possibility of using R plotting
capabilities from external (C) code. They have several plotting
functions, implemented in R, that are needed to be included in a
front-end Windows-based applicatio
On Fri, Dec 12, 2008 at 4:35 PM, wrote:
> do extra to specify otherwise. One of the standard references for regular =
> expressions if you really want to understand what is going on is "Mastering=
> Regular Expressions" by Jeffrey Friedl. You should really read through th=
There are also regu
Where do you get "should" and "expect" from? All the regular expression to=
ols that I am familiar with only match non-overlapping patterns unless you =
do extra to specify otherwise. One of the standard references for regular =
expressions if you really want to understand what is going on is "Ma
Where do you get "should" and "expect" from? All the regular expression tools
that I am familiar with only match non-overlapping patterns unless you do extra
to specify otherwise. One of the standard references for regular expressions
if you really want to understand what is going on is "Maste
Mathieu Ribatet epfl.ch> writes:
>
> Dear Terry,
>
> One way to locate which file is wrong - surely not the most brillant
> way! You could do an R script that sources each of your .R files within
> a "for (file in file.names)" loop.
> When R will stop, it will indicate which file has a wrong
Please do your own homework: the help page says
For 'gregexpr' a list of the same length as 'text' each element of
which is an integer vector as in 'regexpr', except that the
starting positions of every (disjoint) match are given.
If that
Full_Name: Reid Thompson
Version: 2.8.0 RC (2008-10-12 r46696)
OS: darwin9.5.0
Submission from: (NULL) (129.98.107.177)
the gregexpr() function does NOT return a complete list of global matches as it
should. this occurs when a pattern matches two overlapping portions of a
string, only the first
On Fri, 12 Dec 2008, Spencer Graves wrote:
Hello:
For the record, I found the source of this warning: I had an
extraneous space in "\item{fd} {text}": When I changed to "\item{fd}{text}",
this warning disappeared.
And while you've been away you missed
https://stat.ethz.ch/pipermail/r-
Hello:
For the record, I found the source of this warning: I had an
extraneous space in "\item{fd} {text}": When I changed to
"\item{fd}{text}", this warning disappeared.
Best Wishes,
Spencer
#
What might be the problem generating message
I think the /tmp file gets removed:
ERROR: lazy loading failed for package 'xts'
** Removing '/private/tmp/Rinst625532301/xts'
ERROR
Installation failed.
Removing '/tmp/Rinst625532301'
At least it seems to when I run R CMD from the shell.
>
> Yes, there are several options for not distributing
You have missed the following item in NEWS for R-patched.
NEW FEATURES
o qt() now works for 0 < df < 1.
Please review what the FAQ has to say about checkiong your facts and not
reporting things which are already fixed.
Fortunately this example had some use: it showed someone had repla
Jeff Ryan wrote:
A quick comment on two subjects:
First to get the line # from the command line:
cat pkg/R/* > all.R
wc all.R
vim +LINE all.R (or pick you favorite method here...)
The tmp file is also indicated in error message, so you can edit that,
go to the line number, find context, g
A quick comment on two subjects:
First to get the line # from the command line:
cat pkg/R/* > all.R
wc all.R
vim +LINE all.R (or pick you favorite method here...)
>From there it should be easy enough to get context. At least enough
to grep back into the R directory.
Also, the use of unit-test
Duncan Murdoch wrote:
On 11/12/2008 6:04 PM, Terry Therneau wrote:
I'm making the move of the survival package from my own environment to,
and have stumbled into a vacuum. The R Extensions manual has really
nice
instructions about how to lay out the directories, order the files, and
run
Thanks to all for the replys. I've learned several things
First -- I didn't miss anything obvious in the documentation. This is good in
one sense at least: I wasn't being blind. I had one misunderstanding pointed
out, which is that I need not worry about my test suite being run with each
INS
Using parse() is better for syntax errors;
pathnames <- list.files(path="pkg/R", pattern="[.](r|R|s|S)$", full.names=TRUE);
for (pathname in pathnames) parse(pathname)
/Henrik
On Thu, Dec 11, 2008 at 4:00 PM, Duncan Murdoch wrote:
> On 11/12/2008 6:04 PM, Terry Therneau wrote:
>>
>> I'm making
On Fri, 12 Dec 2008, Peter Dalgaard wrote:
Prof Brian Ripley wrote:
I have never seen the report in the repository. There were problems with
R-bugs at around that time (most email submission was stalled for a month
or so).
Maybe, but I don't see a PR# on _any_ of Martin Morgan's posts...
Prof Brian Ripley wrote:
I have never seen the report in the repository. There were problems
with R-bugs at around that time (most email submission was stalled for a
month or so).
Maybe, but I don't see a PR# on _any_ of Martin Morgan's posts...
However, I think the problems are far more se
I have never seen the report in the repository. There were problems with
R-bugs at around that time (most email submission was stalled for a month
or so).
However, I think the problems are far more serious: the help page says
Returns a matrix of integers indicating their column number in
19 matches
Mail list logo
