Martin Morgan wrote:
> > Do you know if this is all happening inside a C function that could
> > handle disabling and enabling GC? Or would it require doing this at
> > the R level? For testing, I am turning GC on and off at the R level
> Generally complicated operations across multiple functi
Martin Morgan wrote:
> On 11/14/2011 11:47 AM, dhi...@sonic.net wrote:
> > dhi...@sonic.net wrote:
> >> Martin Morgan wrote:
> >
> > I had done some google searches on this issue, since it seemed like it
> > should not be too uncommon, but the only other hit I could come up
> > with was a thread
dhi...@sonic.net wrote:
> Martin Morgan wrote:
> > Allocating many small objects triggers numerous garbage collections as R
> > grows its memory, seriously degrading performance. The specific use case
> > is in creating a STRSXP of several 1,000,000's of elements of 60-100
> > characters each;
Martin Morgan wrote:
> Allocating many small objects triggers numerous garbage collections as R
> grows its memory, seriously degrading performance. The specific use case
> is in creating a STRSXP of several 1,000,000's of elements of 60-100
> characters each; a simplified illustration understa
Erik Iverson wrote:
> dhi...@sonic.net wrote:
> > This might be a dumb question, but I couldn't figure out how to find
> > the answer: why is it that comments in R documentation files (i.e. in
> > examples) typically start with a double hash (##) instead of a single
> > hash?
> See the second pa
This might be a dumb question, but I couldn't figure out how to find
the answer: why is it that comments in R documentation files (i.e. in
examples) typically start with a double hash (##) instead of a single
hash?
-- Dave
__
R-devel@r-project.org maili
[EMAIL PROTECTED] wrote:
> /opt/oracle/product/10g/lib/libclntst10.a: file not recognized: File truncated
Here:
http://osdir.com/ml/lang.r.mac/2006-08/msg00031.html
I found a suggestion to do this:
$ cd $ORACLE_HOME/bin
$ ./genclntst
-- Dave
__
[EMAIL PROTECTED] wrote:
> doesn't:
> dbGetQuery(conn, "\nselect * from dual")
> dbGetQuery(conn, "select\n * from dual")
> dbGetQuery(conn, "/* comment */ select * from dual")
This sounds like my doing. What version of Oracle are you using?
Oracle 9i has a bug that interferes with the docume
Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> I just updated my copy of Cygwin to the latest version, and now Windows
> builds are failing on that machine. The only parts of the R toolset I
> changed were the Cygwin dlls. I haven't tracked down exactly what the
> problem is, and probably won't b
Full_Name: David Hinds
Version: 2.4.0
OS: Windows XP
Submission from: (NULL) (64.168.232.238)
A (maybe naive) use of tryCatch to trap errors and report as warnings does not
work, i.e.:
x <- tryCatch(lm(xyzzy), error=warning)
In src/library/base/R/stop.R, the warning() function contains the fo
I'm using R-2.3.1 but the code in question is the same in the
01-Oct-2006 snapshot for release 2.4.0. I'd like to evaluate an
expression, catching errors and handling them as warnings. My first
attempt:
x <- tryCatch(lm(xyzzy), error=warning)
didn't work; the error is still treated as an err
Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> The current R-exts.texi has
> AC_INIT([RODBC], 1.1.4) dnl package name, version
> and that is crucially different from your example. Autoconf 2.59 has a
> barely documented back-compatibility mode than is invoked for AC_INIT with
> just one argume
I've been working with raw vectors quite a bit and was wondering if
the R team might comment on where they see raw vector support going in
the long run. Is the intent that 'raw' will eventually become a first
class data type on the same level as 'integer'? Or should 'raw' have
more limited suppo
Here's an update of my rawConnection() implementation. In addition to
providing a raw version of textConnection(), this fixes two existing
issues with textConnection(): one is that the current textConnection()
implementation carries around unprotected SEXP pointers, the other is
a performance prob
Luke Tierney <[EMAIL PROTECTED]> wrote:
> I am not comfortable making this available at this point. It might be
> useful to have but would need careful thought. Without some way to
> find out the true length there are potential problems. Without some
> way of making sure the fields in VECSXP an
Luke Tierney <[EMAIL PROTECTED]> wrote:
> It might or might not work now but is not guaranteed to do so reliably
> in the future. Seeing the risks of leaving SETLENGTH exposed, it is
> very likely that SETLENGTH will be removed from the sources after the
> 2.2.0 release.
> If you provide your ow
Can someone explain the use of SETLENGTH() and SETTRUELENGTH()?
I would like to allocate a vector and reserve some space at the end,
so that it appears shorter than the allocated size. So that I can
more efficiently append to the vector, without requiring a new copy
every time. So I'd like to use
Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> Probably! The differences I still know about are:
> - I'd like the name to reflect the data source, so rawConnection or
> something similar rather than overloading textConnection.
> - It needs a man page, or to be included on the textConnection m
Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> I think the cost of duplicating as.raw is worse than the cost of using
> extra memory. If the lack of symmetry bothers you, a solution is to
> require a raw object as input.
It wouldn't exactly be duplicating as.raw since this way of converting
to ra
Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> >
> > Having a rawConnection() entry point is simple enough. Seeking also
> > seems straightforward. I'm not so sure about using as.raw(). I
> > wondered about that, but also thought that rather than coercing to
> > raw, it might make more sense to ca
Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> I would implement it differently from the way you did. I'd call it
> a rawConnection, taking a raw variable (or converting something else
> using as.raw) as the input, and providing both text and binary
> read/write modes (using the same conventions for
Martin Maechler <[EMAIL PROTECTED]> wrote:
> I think the main point of David's proposal is still worth
> consideration: One way to see text connections is as a way to
> treat some kind of R objects as "generalized files" i.e., connections.
To summarize the motivation for the proposal, again:
-
Gabor Grothendieck <[EMAIL PROTECTED]> wrote:
> Just to be concrete, suppose one wants to run the following as a
> concurrent process to R. (What is does is it implicitly sets x to
> zero and then for each line of stdin it adds the first field of the
> input to x and prints that to stdout unless
Chris Paulse <[EMAIL PROTECTED]> wrote:
> Hi,
> I'm sure that this question has come up many times before. When I load an R
> extension dll I've built with the Microsoft compiler, I get the warning:
> Warning message:
> DLL attempted to change FPU control word from 8001f to 9001f
I think maybe
Martin Maechler <[EMAIL PROTECTED]> wrote:
> In the mean time, I think it has become clear that
> "loopconnection" isn't necessarily a better name, and that
> textConnection() has been there in "the S litterature" for a
> good reason and for quite a while.
> Let's forget about the naming and the e
Gabor Grothendieck <[EMAIL PROTECTED]> wrote:
> OK. I guess you want one of the core people to respond but in the
> interim can you explain the terminology "loop"?
> Also, do you have any prototypical applications in mind?
"loop" is short for "loopback". A loop or loopback device is one that
I accidentally left one small change out of my previous patch.
So... no response to my request for comments. Does that mean no one
has an opinion about whether this is a good idea or not? I'd
appreciate a response from an R core member one way or the other; if
this is not the right way to get a
[EMAIL PROTECTED] wrote:
> On Wed, 24 Aug 2005 [EMAIL PROTECTED] wrote:
> > I just downloaded the file
> >
> > ftp://ftp.stat.math.ethz.ch/Software/R/R-devel.tar.gz
> >
> > and within proc.time.Rd, the second paragraph of the \value
> > section contains a typo:
> I believe your understanding of t
I've just implemented a generalization of R's text connections, to
also support reading/writing raw binary data. There is very little
new code to speak of. For input connections, I wrote code to populate
the old text connection buffer from a raw vector, and provided a new
raw_read() method. For
29 matches
Mail list logo
