[Rd] To use breaktodebugger(), which file should I include in C code?

Hi, I have tried several headers in RHOME/include , but none of them seemed to work . Thanks for your help. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] To use breaktodebugger(), which file should I include in C code?

On 4/25/2007 3:47 AM, Tong Wang wrote: > Hi, > I have tried several headers in RHOME/include , but none of them seemed > to work . > > Thanks for your help. It's not part of the API, so you can't call it from package code. But the implementation is very simple in Windows: void breaktodeb

[Rd] R-2.5.0 and unlink/wildcards

It seems unlink doesn't work with wildcards in 2.5.0. I've tried R-2.5.0 under gnu/linux from source and the Mac binary from att research. Example: > dir() [1] "bgx.Rnw" "bgx.pdf" "run.1" > unlink("run.*",recursive=T) > dir() [1] "bgx.Rnw" "bgx.pdf" "run.1" > unlink("run.1",recursive=T) >

Re: [Rd] R-2.5.0 and unlink/wildcards

This is shell-dependent on a Unix-alike, but Sys.glob() should work. So try unlink(Sys.glob("run.*"), recursive=TRUE) On Wed, 25 Apr 2007, Ernest Turro wrote: > It seems unlink doesn't work with wildcards in 2.5.0. I've tried > R-2.5.0 under gnu/linux from source and the Mac binary from att >

Re: [Rd] R-2.5.0 and unlink/wildcards

Thanks, this now works. I'd just like to mention that Sys.glob() wasn't necessary in 2.4.1 and this potential requirement should perhaps be mentioned in ?unlink. Thanks E On 25 Apr 2007, at 12:38, Prof Brian Ripley wrote: > This is shell-dependent on a Unix-alike, but Sys.glob() should > w

Re: [Rd] R-2.5.0 and unlink/wildcards

Ernest Turro wrote: > It seems unlink doesn't work with wildcards in 2.5.0. I've tried > R-2.5.0 under gnu/linux from source and the Mac binary from att > research. Example: > > > dir() > [1] "bgx.Rnw" "bgx.pdf" "run.1" > > unlink("run.*",recursive=T) > > dir() > [1] "bgx.Rnw" "bgx.pdf" "run

Re: [Rd] R-2.5.0 and unlink/wildcards

On Wed, 25 Apr 2007, Peter Dalgaard wrote: > Ernest Turro wrote: >> It seems unlink doesn't work with wildcards in 2.5.0. I've tried >> R-2.5.0 under gnu/linux from source and the Mac binary from att >> research. Example: >> >> > dir() >> [1] "bgx.Rnw" "bgx.pdf" "run.1" >> > unlink("run.*",recursi

Re: [Rd] [R] Coercing data types for use in model.frame

Moved to R-devel What is the 'data class'? In particular what is its underlying type? And where in model.frame[.default] are you trying to use it (in the formula, data, in ..., etc). This is an example of where some reproducible code and the error messages would be very helpful indeed.

Re: [Rd] [R] Coercing data types for use in model.frame

Prof Brian Ripley wrote: > Moved to R-devel > > What is the 'data class'? In particular what is its underlying type? > And where in model.frame[.default] are you trying to use it (in the > formula, data, in ..., etc). > > This is an example of where some reproducible code and the error >

[Rd] identify() and metafile copies under Windows XP (PR#9634)

I am running R version as follows under Windows XP. platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status major 2

[Rd] R-exts.texi typo

Index: doc/manual/R-exts.texi === --- doc/manual/R-exts.texi (revision 41314) +++ doc/manual/R-exts.texi (working copy) @@ -8951,7 +8951,7 @@ @deftypefun int R_ReadConsole (char [EMAIL PROTECTED], unsigned char [EMAIL PROT

Re: [Rd] identify() and metafile copies under Windows XP (PR#9634)

This seems not specific to metafiles, nor even to Windows (but the use of Esc is specific to Rgui). As I understand it you expected the results of a graphics operation you interrupted to be copied. I don't see anything on the help page explaining what happens if you interrupt during identify()