Re: [Rd] SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?

2014-12-11 Thread Henrik Bengtsson
On Thu, Dec 11, 2014 at 10:47 AM, Duncan Murdoch wrote: > On 11/12/2014 12:59 PM, Henrik Bengtsson wrote: >> >> SUGGESTION: >> Would it make sense if install.packages() and friends always use an >> "ascii"(*) encoding when parse():ing R package source code files? > > > I think that would be a step

[Rd] Significant memory leak when using XML on Windows

2014-12-11 Thread Janko Thyson
Dear list, I'm sorry to keep coming back with this time and time again, but this bug is still not fixed even though the root cause of the issue has been around for 2-3 years now. And as the number of packages that depend on XML grows, I thought maybe this deserves some wider attention. I did my b

Re: [Rd] SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?

2014-12-11 Thread Duncan Murdoch
On 11/12/2014 12:59 PM, Henrik Bengtsson wrote: SUGGESTION: Would it make sense if install.packages() and friends always use an "ascii"(*) encoding when parse():ing R package source code files? I think that would be a step backwards. It would be better to accept other encodings. As an Englis

[Rd] SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?

2014-12-11 Thread Henrik Bengtsson
SUGGESTION: Would it make sense if install.packages() and friends always use an "ascii"(*) encoding when parse():ing R package source code files? I believe this should be safe, because R code files should be in ASCII [http://en.wikipedia.org/wiki/ASCII] and only in source-code comments you may use

Re: [Rd] Fwd: No source view when using gdb

2014-12-11 Thread Pierrick Bruneau
Works like a charm, thanks! On Thu, Dec 11, 2014 at 3:00 PM, Martyn Plummer wrote: > On Thu, 2014-12-11 at 14:00 +0100, Pierrick Bruneau wrote: >> Dear R contributors, >> >> Say I want to debug some C code invoked through .Call() - say >> "varbayes" in the VBmix package. following the instruction

Re: [Rd] Fwd: No source view when using gdb

2014-12-11 Thread Martyn Plummer
On Thu, 2014-12-11 at 14:00 +0100, Pierrick Bruneau wrote: > Dear R contributors, > > Say I want to debug some C code invoked through .Call() - say > "varbayes" in the VBmix package. following the instructions in > "Writing R Extensions", I perform the following actions : > > R -d gdb > run > lib

[Rd] Fwd: No source view when using gdb

2014-12-11 Thread Pierrick Bruneau
Dear R contributors, Say I want to debug some C code invoked through .Call() - say "varbayes" in the VBmix package. following the instructions in "Writing R Extensions", I perform the following actions : R -d gdb run library(VBmix) CTRL+C break varbayes signal 0 mod <- varbayes(as.matrix(iris)[,1

[Rd] package.skeleton leads to R CMD check aborting

2014-12-11 Thread Dirk Eddelbuettel
The package.skeleton() base function is useful for creating empty packages. The fact that the help files generated by the function cause errors was long an annoyance, but I noticed last month (while preparing for a workshop on R and packages) that it creates packages which cause 'R CMD check ...'

Re: [Rd] R CMD check --as-cran and (a)spell checking

2014-12-11 Thread Martin Maechler
> Henrik Bengtsson > on Fri, 5 Dec 2014 18:17:57 -0800 writes: > Does anyone know if it is possible to add a dictionary > file of known words that becomes part of the *built* > package to tell 'R CMD check --as-cran' not to report > these words as misspelled. I want t