Dear Prof. Ripley,
>> I have discovered that my cat function cannot write more than 1
>> characters to a text file.
> You mean on a single line?
Yes. OOo tries to save space...
> No, works for me on Mac OS X and x86_64 Fedora 8 (as does 10x larger).
> Can you run this under a debugger and find
Prof Brian Ripley wrote:
I think you meant \describe
On Mon, 5 Jan 2009, Robin Hankin wrote:
Hi
The aylmer package generates a warning (under R-2.9.0) for an Rd file
which I think is OK.
The package is clean under R-2.8.1.
Did you actually look at the help under 2.8.1: it is I am sur
I think you meant \describe
On Mon, 5 Jan 2009, Robin Hankin wrote:
Hi
I make a point of going through my packages every so often and perusing
the check results on CRAN.
The aylmer package generates a warning (under R-2.9.0) for an Rd file which I
think is OK.
The package is clean unde
Hi
I make a point of going through my packages every so often and perusing
the check results on CRAN.
The aylmer package generates a warning (under R-2.9.0) for an Rd file
which I think is OK.
The package is clean under R-2.8.1.
Specifically, the warning is:
* checking Rd files ... OK
On Mon, 5 Jan 2009, Prof Brian Ripley wrote:
Turn off "keep.source": you will see that is foo that is changed by the call.
Something is either not setting or handling the NAMED field and so not
duplicating: it looks like the pairlist code for $<- is the culprit.
Yes, so try a current R-deve
You will have to read more carefully: an ENVSXP is nothing like a VECSXP,
and does not have the names of its entries in a names attribute.
You access variables in an environment via findVar() and friends,
including findVarInFrame: see 'Writing R Extensions'.
On Mon, 5 Jan 2009, torpedo fisken
Turn off "keep.source": you will see that is foo that is changed by the
call.
Something is either not setting or handling the NAMED field and so not
duplicating: it looks like the pairlist code for $<- is the culprit.
On Mon, 5 Jan 2009, Felix Andrews wrote:
Hi list(...),
I've narrowed do
Hi,
I'm quite knew in R, so I might not have the R specific jargon.
But here is my problem,
I'm trying to access and use variabels given by a function environment,
more specifically the rho in do_optim in src/main/optim.c
According to the documentation
http://cran.r-project.org/doc/manuals/R-ints
Hi list(...),
I've narrowed down a weird bug. It's like a ghost in the machine, in
that functions seem to remember things that they should not be able
to. In the example below, the result of the second (and subseqent)
calls depend on what was given in the first call.
foo <- function(given = NULL)
On Sun, 4 Jan 2009, Daniel Sabanés Bové wrote:
Hi,
during the examination of a Sweave hang-up inside an odfWeave call (OOo
XMLs have looong lines) I have discovered that my cat function cannot
write more than 1 characters to a text file. Otherwise, the internal
You mean on a single line?
Hi,
during the examination of a Sweave hang-up inside an odfWeave call (OOo
XMLs have looong lines) I have discovered that my cat function cannot
write more than 1 characters to a text file. Otherwise, the internal
C code causes a hang-up, which can only be stopped with a quit signal
that term
On Sun, 4 Jan 2009, Jan de Leeuw wrote:
Thanks. Works with a previous version of texinfo.tex from Time Machine.
If you run tlmgr you'll see that CTAN now has the (broken) 2009-01-01
version, released by the FSF in 2009.
That is not how I read it: if I search on CTAN for texinfo.tex I get to
12 matches
Mail list logo
