My solution the original post is to always set 'con - NULL' after closing a
connection, and then test for NULL. This is how I do to make sure to make
sure that opened connections are closed and as soon as possible.
foo - function(...) {
con - file(foo.R, open=r):
on.exit({
if
On Thu, 15 Nov 2007, Adrian Dusa wrote:
On Thursday 15 November 2007, Prof Brian Ripley wrote:
[...]
Using as above:
\code{\link{anova}}
the html help file directs to
file:///home/adi/myRlibrary/stats/html/anova.html
I hope it is actually ../../stats/html/anova.html and the browser is
On Thu, 15 Nov 2007, Prof Brian Ripley wrote:
On Thu, 15 Nov 2007, Adrian Dusa wrote:
On Thursday 15 November 2007, Prof Brian Ripley wrote:
[...]
Using as above:
\code{\link{anova}}
the html help file directs to
file:///home/adi/myRlibrary/stats/html/anova.html
I hope it is actually
Gabor Grothendieck ggrothendieck at gmail.com writes:
inst/NEWS would have the advantage of consistency with R itself
which also has a NEWS file.
...
My vote is for inst/ChangeLog.
I wote for inst/NEWS, while inst/ChangeLog can also be present to show more
details such as svn log.
Gregor
Prof Brian Ripley wrote:
On Wed, 14 Nov 2007, Bjørn-Helge Mevik wrote:
When should one specify LazyLoad, LazyData, and ZipData?
Preferably always, and I would suggest all should be 'yes' if your
package will work with them.
Thank you! After reading this, and the very nice R-news article
I think that's right -- it only works on NTFS systems. This page
refers to it as an NTFS symbolic link:
http://en.wikipedia.org/wiki/NTFS_symbolic_link
On Nov 14, 2007 10:00 PM, Duncan Murdoch [EMAIL PROTECTED] wrote:
On 14/11/2007 7:44 PM, Gabor Grothendieck wrote:
On Nov 14, 2007 4:36 PM,
On Thursday 15 November 2007, Prof Brian Ripley wrote:
[...]
help.start()
I got it.
Perhaps it would be useful to have another startup option, something
like: options(htmlLinksResolve=TRUE)
that one could use in the .First() function from .Rprofile
You could have a function to
Upon further consideration, I realized there is a philosophical element
here---if a connection is closed and hence does not exist, is it open?
The practical issue for me is that when you do something like
close(con)
the 'con' object is still lying around and is essentially undefined. For
In-line omments near the end:
On Wed, 14 Nov 2007, Martin Maechler wrote:
still found a bit time for more remarks.
MM == Martin Mächler [EMAIL PROTECTED]
on Wed, 14 Nov 2007 14:23:12 +0100 (CET) writes:
MM On Wed, November 14, 2007 09:09, Prof Brian Ripley
MM wrote:
On Tue,
On Nov 14, 2007, at 11:55 PM, Gabor Grothendieck wrote:
inst/NEWS would have the advantage of consistency with R itself
which also has a NEWS file.
I vote for NEWS for reasons above plus because that's what I use in my
packages already ;).
IMHO it should be installed automatically if
On 11/15/2007 9:57 AM, Simon Urbanek wrote:
On Nov 14, 2007, at 11:55 PM, Gabor Grothendieck wrote:
inst/NEWS would have the advantage of consistency with R itself
which also has a NEWS file.
I vote for NEWS for reasons above plus because that's what I use in my
packages already ;).
On Nov 15, 2007 9:57 AM, Simon Urbanek [EMAIL PROTECTED] wrote:
On Nov 14, 2007, at 11:55 PM, Gabor Grothendieck wrote:
inst/NEWS would have the advantage of consistency with R itself
which also has a NEWS file.
I vote for NEWS for reasons above plus because that's what I use in my
I'd support a change, to having a closed-but-not-invalid status for a
'rw' connection, and to have a usable 'isOpen'. The suggestion of
relying on user-code to always housekeep after calling 'close', eg by
setting to NULL, seems a bit risky as a guideline for R as a whole (one
can never tell what
Hey All,
I was wondering if I could solicit a little advice. I have been
experiencing some quirkiness in my C code through .Call.
Unfortunately, my program is rather large, so I'm trying to create a
brief example. Yet before I do, I thought maybe a conceptual question
would be sufficient.
You assume that when you call any of those functions its arguments are
protected (as it is the case when the function is called from within R).
However, I do not see why they would be if you do not do it explicitly.
Therefore, it is very likely that a result of one function, used in turn
in a call
On Thu, Nov 15, 2007 at 11:53:53PM +, Oleg Sklyar wrote:
You assume that when you call any of those functions its arguments are
protected (as it is the case when the function is called from within R).
However, I do not see why they would be if you do not do it explicitly.
Therefore, it is
On Nov 15, 2007, at 10:53 AM, Duncan Murdoch wrote:
On 11/15/2007 9:57 AM, Simon Urbanek wrote:
On Nov 14, 2007, at 11:55 PM, Gabor Grothendieck wrote:
inst/NEWS would have the advantage of consistency with R itself
which also has a NEWS file.
I vote for NEWS for reasons above plus
17 matches
Mail list logo
