Displaying 20 results from an estimated 61 matches for "lgautier".
Did you mean:
gautier
2018 Oct 07
4
Warning when calling formals() for `[`.
...x operators, "[[", "[<-", "[[<-" are similar
>
> The docs are pretty clear that args() on a primitive should yield a closure, so at least the documentation seems to be wrong.
>
> -pd
>
>
>> On 6 Oct 2018, at 19:26 , Laurent Gautier <lgautier at gmail.com> wrote:
>>
>> Hi,
>>
>> A short code example showing the warning might the only thing needed here:
>>
>> ```
>>> formals(args(`[`))
>> NULL
>>
>> *Warning message:In formals(fun) : argument is not a function*
>>>...
2019 Nov 30
2
Inconsistent behavior for the C AP's R_ParseVector() ?
...quot;"]] <- 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
when using `[[<` ?
Best,
Laurent
Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier <lgautier at gmail.com> a ?crit :
> I found the following code comment in `src/main/gram.c`:
>
> ```
>
> /* Memory leak
>
> yyparse(), as generated by bison, allocates extra space for the parser
> stack using malloc(). Unfortunately this means that there is a memory
> leak in c...
2019 Dec 07
2
Inconsistent behavior for the C AP's R_ParseVector() ?
...le name
> > ```
> >
> > Should the parser be made to accept as valid what is otherwise possible
> > when using `[[<` ?
> >
> >
> > Best,
> >
> > Laurent
> >
> >
> >
> > Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier <lgautier at gmail.com> a
> ?crit :
> >
> >> I found the following code comment in `src/main/gram.c`:
> >>
> >> ```
> >>
> >> /* Memory leak
> >>
> >> yyparse(), as generated by bison, allocates extra space for the parser
> >>...
2019 Dec 09
0
Inconsistent behavior for the C AP's R_ParseVector() ?
...r be made to accept as valid what is otherwise
> possible
> > when using `[[<` ?
> >
> >
> > Best,
> >
> > Laurent
> >
> >
> >
> > Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier
> <lgautier at gmail.com <mailto:lgautier at gmail.com>> a ?crit :
> >
> >> I found the following code comment in `src/main/gram.c`:
> >>
> >> ```
> >>
> >> /* Memory leak
> >>
> >> yyparse(), as gener...
2017 Jan 02
1
Definition of uintptr_t in Rinterface.h
> 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 e...
2008 May 19
1
(PR#11484) On WinXP, R CMD config needs sh (and breaks without it)
....
I guess that I have been lucky with the "potential" aspect of the
requirements so far.
Is there a documentation of what is needed by the respective R CMD flavors ?
> R CMD config is primarily intended to be used in configure scripts in
> packages.
>
> On Sun, 18 May 2008, lgautier at gmail.com wrote:
>
>> Full_Name: Laurent Gautier
>> Version: R-2.7.0patched (r45712)
>> OS: WinXP
>> Submission from: (NULL) (90.15.141.247)
>>
>>
>>
>> On a WinXP box (that does not has "sh" in the %Path%,
>> R CMD config appear...
2019 Dec 09
0
Inconsistent behavior for the C AP's R_ParseVector() ?
...hen using `[[<` ?
>> >
>> >
>> > Best,
>> >
>> > Laurent
>> >
>> >
>> >
>> > Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier
>> <lgautier at gmail.com <mailto:lgautier at gmail.com>> a ?crit :
>> >
>> >> I found the following code comment in `src/main/gram.c`:
>> >>
>> >> ```
>> >>
>> >> /* Memory leak
>>...
2019 Nov 30
2
Inconsistent behavior for the C AP's R_ParseVector() ?
Hi,
The behavior of
```
SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP);
```
defined in `src/include/R_ext/Parse.h` appears to be inconsistent depending
on the string to be parsed.
Trying to parse a string such as `"list(''=1+"` sets the
`ParseStatus` to incomplete parsing error but trying to parse
`"list(''=123"` will result in R sending a message to the
2017 Jan 01
3
Definition of uintptr_t in Rinterface.h
...o define HAVE_UINTPTR_T appropriately.'
AFAICS if you comply, there will not be a conflict.
Also note that is only an issue if CSTACK_DEFNS is defined, not the
default and not mentioned here.
> 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 Rinterface.h can be conflicting
>> with a definition in stdint.h:
>>
>> /usr/include/R/Rinterface.h has:
>> typedef unsigned long uintptr_t;
>>
>> /usr...
2019 Dec 14
1
Inconsistent behavior for the C AP's R_ParseVector() ?
...your is just one of many that can occur - any R API
> call that does allocation (and parsing obviously does) can cause errors.
> Note that this is true for pretty much all R API functions.
>
> Cheers,
> Simon
>
>
>
> > On Dec 14, 2019, at 11:25 AM, Laurent Gautier <lgautier at gmail.com>
> wrote:
> >
> > 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...
2016 Dec 27
3
Definition of uintptr_t in Rinterface.h
Hi,
I was recently pointed out that a definition in Rinterface.h can be conflicting
with a definition in stdint.h:
/usr/include/R/Rinterface.h has:
typedef unsigned long uintptr_t;
/usr/include/stdint.h has:
typedef unsigned int uintptr_t;
(when 32bit platform complete definition is:
#if __WORDSIZE == 64
# ifndef __intptr_t_defined
typedef long int intptr_t;
# define
2019 Dec 14
2
Inconsistent behavior for the C AP's R_ParseVector() ?
...valid what is otherwise possible
>>> > when using `[[<` ?
>>> >
>>> >
>>> > Best,
>>> >
>>> > Laurent
>>> >
>>> >
>>> >
>>> > Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier <lgautier at gmail.com> a
>>> ?crit :
>>> >
>>> >> I found the following code comment in `src/main/gram.c`:
>>> >>
>>> >> ```
>>> >>
>>> >> /* Memory leak
>>> >>
>>> >> yyparse(),...
2019 Dec 09
3
Inconsistent behavior for the C AP's R_ParseVector() ?
...; Should the parser be made to accept as valid what is otherwise possible
>> > when using `[[<` ?
>> >
>> >
>> > Best,
>> >
>> > Laurent
>> >
>> >
>> >
>> > Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier <lgautier at gmail.com> a
>> ?crit :
>> >
>> >> I found the following code comment in `src/main/gram.c`:
>> >>
>> >> ```
>> >>
>> >> /* Memory leak
>> >>
>> >> yyparse(), as generated by bison, allocates ext...
2023 Apr 26
1
Warnings created during R_eval or R_tryEval not shown before R ending or R 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()...
2019 Dec 02
0
Inconsistent behavior for the C AP's R_ParseVector() ?
...t("" = 1)
> Error: attempt to use zero-length variable name
> ```
>
> Should the parser be made to accept as valid what is otherwise possible
> when using `[[<` ?
>
>
> Best,
>
> Laurent
>
>
>
> Le sam. 30 nov. 2019 ? 17:33, Laurent Gautier <lgautier at gmail.com> a ?crit :
>
>> I found the following code comment in `src/main/gram.c`:
>>
>> ```
>>
>> /* Memory leak
>>
>> yyparse(), as generated by bison, allocates extra space for the parser
>> stack using malloc(). Unfortunately this means t...
2019 Dec 14
0
Inconsistent behavior for the C AP's R_ParseVector() ?
...dded R). There are many different errors, your is just one of many that can occur - any R API call that does allocation (and parsing obviously does) can cause errors. Note that this is true for pretty much all R API functions.
Cheers,
Simon
> On Dec 14, 2019, at 11:25 AM, Laurent Gautier <lgautier at gmail.com> wrote:
>
> 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....
2019 Sep 08
1
Error: package or namespace load failed for ‘utils
...gt; customize R, e.g. for class use. Rscript also checks the environment
> variable R_SCRIPT_DEFAULT_PACKAGES; if set, this takes precedence over
> R_DEFAULT_PACKAGES.
> Bill Dunlap
> TIBCO Software
> wdunlap tibco.com
>
>
> On Sun, Sep 8, 2019 at 8:42 AM Laurent Gautier <lgautier at gmail.com> wrote:
>
>> Hi,
>>
>> When starting an embedded R I encounter the following issue under certain
>> conditions:
>>
>> ```
>> Error: package or namespace load failed for ?utils? in if (.identC(class1,
>> class2) || .identC(class2, &q...
2018 Oct 07
1
Warning when calling formals() for `[`.
...x operators, "[[", "[<-", "[[<-" are similar
>>> The docs are pretty clear that args() on a primitive should yield a closure, so at least the documentation seems to be wrong.
>>> -pd
>>>> On 6 Oct 2018, at 19:26 , Laurent Gautier <lgautier at gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> A short code example showing the warning might the only thing needed here:
>>>>
>>>> ```
>>>>> formals(args(`[`))
>>>> NULL
>>>>
>>>...
2019 Sep 08
6
Error: package or namespace load failed for ‘utils
Hi,
When starting an embedded R I encounter the following issue under certain
conditions:
```
Error: package or namespace load failed for ?utils? in if (.identC(class1,
class2) || .identC(class2, "ANY")) TRUE else {:
missing value where TRUE/FALSE needed
```
(more such errors for grDevices, graphics, and stats)
And in the end:
```
Warning messages:
1: package ?utils? in
2018 Oct 06
5
Warning when calling formals() for `[`.
Hi,
A short code example showing the warning might the only thing needed here:
```
> formals(args(`[`))
NULL
*Warning message:In formals(fun) : argument is not a function*
> is.function(`[`)
[1] TRUE
> is.primitive(`[`)
[1] TRUE
```
Now with an other primitive:
```
> formals(args(`sum`))
$...
$na.rm
[1] FALSE
> is.function(`sum`)
[1] TRUE
> is.primitive(`sum`)
[1] TRUE