search for: shomron

...(=failure) or SEXP. It may be even perhaps useful to declare it as a separate type to make this clearer, but I don't think it was really necessary so far. Any other cases where a SEXP value somehow escapes as NULL should be considered a bug. Cheers, Simon > On 30/07/2024, at 2:54 PM, Erez Shomron <r-mails at erezsh.org> wrote: > > Thank you Ivan, > > At this point, without it being documented explicitly, I tend to lean on the safe side. > > If the non-null assumption is ever incorrect, on debug and safe builds unwrapping is an assert that will guarantee to crash R...

...d care about edge cases as well. Last but not least, thanks for sharing your WIP documentation. If you agree, I definitely can use that as a reference as I progress. Best regards, - Erez On Mon, Jul 29, 2024, at 1:23 PM, Ivan Krylov wrote: > ? Sat, 27 Jul 2024 14:36:20 +0300 > "Erez Shomron" <r-mails at erezsh.org> ?????: > > > I'm working on bindings for the API (for zig), and was wondering if > > the R's C API guarantees it won't return null pointers? The only > > reference I found in the "Writing R Extensions" manual where this...

? Sat, 27 Jul 2024 14:36:20 +0300 "Erez Shomron" <r-mails at erezsh.org> ?????: > I'm working on bindings for the API (for zig), and was wondering if > the R's C API guarantees it won't return null pointers? The only > reference I found in the "Writing R Extensions" manual where this not > the case i...

...the hardest kind of code to fix. Remember Kernighan's Law: "Everyone knows that debugging is twice as hard as writing a program in the first place. So if you?re as clever as you can be when you write it, how will you ever debug it?" Duncan Murdoch On 2024-07-05 7:35 a.m., Erez Shomron wrote: > Is the following a bug in your opinion? I think so. > > This works as expected: > > ``` > with(mtcars, plot(wt, mpg, plot.first = { > plot.window(range(wt), range(mpg)) > arrows(3, 15, 4, 30) > })) > ``` > > This does not. > > ``` &gt...

Is the following a bug in your opinion? I think so. This works as expected: ``` with(mtcars, plot(wt, mpg, plot.first = { plot.window(range(wt), range(mpg)) arrows(3, 15, 4, 30) })) ``` This does not. ``` plot(mpg ~ wt, data = mtcars, plot.first = { plot.window(range(wt), range(mpg)) arrows(3, 15, 4, 30) }) ``` With error: ``` Error in arrows(3, 15, 4, 30) : plot.new has not

? Fri, 05 Jul 2024 14:35:40 +0300 "Erez Shomron" <r-mails at erezsh.org> ?????: > This works as expected: > with(mtcars, plot(wt, mpg, plot.first = { > plot.window(range(wt), range(mpg)) > arrows(3, 15, 4, 30) > })) I think you meant panel.first, not plot.first. At least I cannot find any mention of plot.firs...

Hello, I'm working on bindings for the API (for zig), and was wondering if the R's C API guarantees it won't return null pointers? The only reference I found in the "Writing R Extensions" manual where this not the case is `R_tryEval` and `R_tryEvalSilent`. Otherwise it's unclear. The reason I care about this is syntax. Because I don't know whether SEXPs are NULL or

Hello R Core team, As someone who working on bindings to the API, having an index of the public API is a very welcome change. In order to improve the ability for users to explore the API, I would like to propose adding a section of the API Index by category. You already have the functions and variables categorized by section, so I would suggest to use sections as the categories, and inside