similar to: (PR#11484) On WinXP, R CMD config needs sh (and breaks

2008/5/19 Prof Brian Ripley <ripley at stats.ox.ac.uk>: > Where is the bug here? It also does on a Unix-alike. Then "R CMD config --help" could at least spit out an error stating what should be installed (rather than die with an execution error straight from the DOS). Setting an "sh" in the %Path% (sh coming from cygwin) does not seem to lead to something working

> On Jan 1, 2017, at 5:12 PM, Laurent Gautier <lgautier at gmail.com> wrote: > > > > 2017-01-01 8:28 GMT-05:00 Prof Brian Ripley <ripley at stats.ox.ac.uk>: > On 29/12/2016 15:55, Simon Urbanek wrote: > The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback with HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. Should be now

On 12/7/19 10:32 PM, Laurent Gautier wrote: > Thanks for the quick response Tomas. > > The same error is indeed happening when trying to have a zero-length > variable name in an environment. The surprising bit is then "why is > this happening during parsing" (that is why are variables assigned to > an environment) ? The emitted R error (in the R console) is not a

On 12/9/19 2:54 PM, Laurent Gautier wrote: > > > Le?lun. 9 d?c. 2019 ??05:43, Tomas Kalibera <tomas.kalibera at gmail.com > <mailto:tomas.kalibera at gmail.com>> a ?crit?: > > On 12/7/19 10:32 PM, Laurent Gautier wrote: >> Thanks for the quick response Tomas. >> >> The same error is indeed happening when trying to have a >>

Dear Laurent, could you please provide a complete reproducible example where parsing results in a crash of R? Calling parse(text="list(''=123") from R works fine for me (gives Error: attempt to use zero-length variable name). I don't think the problem you observed could be related to the memory leak. The leak is on the heap, not stack. Zero-length names of elements in a

Laurent, the main point here is that ParseVector() just like any other R API has to be called in a correct context since it can raise errors so the issue was that your C code has a bug of not setting R correctly (my guess would be your'e not creating the initial context necessary in embedded R). There are many different errors, your is just one of many that can occur - any R API call that

Hi again, Beside R_ParseVector()'s possible inconsistent behavior, R's handling of zero-length named elements does not seem consistent either: ``` > lst <- list() > lst[[""]] <- 1 > names(lst) [1] "" > list("" = 1) Error: attempt to use zero-length variable name ``` Should the parser be made to accept as valid what is otherwise possible

Hi Simon, Widespread errors would have caught my earlier as the way that code is using only one initialization of the embedded R, is used quite a bit, and is covered by quite a few unit tests. This is the only situation I am aware of in which an error occurs. What is a "correct context", or initial context, the code should from ? Searching for "context" in the R-exts manual

Thanks for the quick response Tomas. The same error is indeed happening when trying to have a zero-length variable name in an environment. The surprising bit is then "why is this happening during parsing" (that is why are variables assigned to an environment) ? We are otherwise aware that the error is not occurring in the R console, but can be traced to a call to R_ParseVector() in

On 29/12/2016 15:55, Simon Urbanek wrote: > The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback with HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. Should be now fixed in R-devel - please check if that works for you. Rconfig.h would be appropriate if Rinterface.h is being included from C code using the same compiler as used for R. But as Rinterface.h

2017-01-01 8:28 GMT-05:00 Prof Brian Ripley <ripley at stats.ox.ac.uk>: > On 29/12/2016 15:55, Simon Urbanek wrote: > >> The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback >> with HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. >> Should be now fixed in R-devel - please check if that works for you. >> > > Rconfig.h

Le lun. 9 d?c. 2019 ? 09:57, Tomas Kalibera <tomas.kalibera at gmail.com> a ?crit : > On 12/9/19 2:54 PM, Laurent Gautier wrote: > > > > Le lun. 9 d?c. 2019 ? 05:43, Tomas Kalibera <tomas.kalibera at gmail.com> a > ?crit : > >> On 12/7/19 10:32 PM, Laurent Gautier wrote: >> >> Thanks for the quick response Tomas. >> >> The same error

? Sun, 23 Apr 2023 13:33:16 -0400 Laurent Gautier <lgautier at gmail.com> ?????: > When tracing what happens during an error I found that > verrorcall_dflt() in src/main/errors.c calls PrintWarnings(). That > function is not part of R's C-API though. I've tried reading the source code and came to a similar conclusion. PrintWarnings() is required for warnings() to work

Laurent, On May 3, 2015, at 8:07 PM, Laurent Gautier <lgautier at gmail.com> wrote: > rPython appears to provide an interface from R to Python by embedding > Python and I'd think that it can safely assume that R has been initialized, > but might not be the point here. > > The issue is that a Python package embedding itself R (here rpy2) appears > to have no way to

Hello, I don't see why you say that the documentation seems to be wrong: class(args(`+`)) #[1] "function" args() on a primitive does return a closure. At least in this case it does. Rui Barradas ?s 14:05 de 07/10/2018, Peter Dalgaard escreveu: > There is more "fun" afoot here, but I don't recall what the point may be: > >> args(get("+"))

Le lun. 9 d?c. 2019 ? 05:43, Tomas Kalibera <tomas.kalibera at gmail.com> a ?crit : > On 12/7/19 10:32 PM, Laurent Gautier wrote: > > Thanks for the quick response Tomas. > > The same error is indeed happening when trying to have a zero-length > variable name in an environment. The surprising bit is then "why is this > happening during parsing" (that is why

Also, check the settings of R_HOME and/or R_LIBS. Bill Dunlap TIBCO Software wdunlap tibco.com On Sun, Sep 8, 2019 at 9:58 AM William Dunlap <wdunlap at tibco.com> wrote: > Look at section 6.1 of the R Installation and Admin manual. > > 6.1 Default packages > > The set of packages loaded on startup is by default > > > getOption("defaultPackages") > [1]

On Wed, Aug 13, 2008 at 6:56 AM, Laurent Gautier <lgautier@gmail.com> wrote: > There is a chance that further changes in the handling of plotting > devices event appear; > I think that there is an ongoing effort to bring new features for R-2.8. > > What about bumping that to r-devel ? (Sorry if you already did and I missed > it). > The solution you came up with could be

The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback with HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. Should be now fixed in R-devel - please check if that works for you. Thanks, Simon > On Dec 26, 2016, at 11:25 PM, Laurent Gautier <lgautier at gmail.com> wrote: > > Hi, > > I was recently pointed out that a definition in

There is more "fun" afoot here, but I don't recall what the point may be: > args(get("+")) function (e1, e2) NULL > args(get("[")) NULL > get("[") .Primitive("[") > get("+") function (e1, e2) .Primitive("+") The other index operators, "[[", "[<-", "[[<-" are similar The