search for: codeberg

...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`. Based on what I've been reading while working on (still very much incomplete) <https://aitap.codeberg.page/R-api>, I think that these are the only two cases where a SEXP can be null, precisely because a null pointer is distinguished from every possible value that could be returned by eval(). Some APIs may accept a null SEXP (with comments in the source code that this is to support some legacy c...

...ot API and probably should not be <...> used". Do you think there is a way to recreate an environment, taking the REFSXP entries into account, without `parent.env<-`? Would you recommend to abandon the folly of unserializing environments manually? -- Best regards, Ivan [1] https://codeberg.org/aitap/unserializeData/src/commit/33d72705c1ee265349b3e369874ce4b47f9cd358/R/unserialize.R#L289-L313

...#39;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`. > > Based on what I've been reading while working on (still very much > incomplete) <https://aitap.codeberg.page/R-api>, I think that these are > the only two cases where a SEXP can be null, precisely because a null > pointer is distinguished from every possible value that could be > returned by eval(). > > Some APIs may accept a null SEXP (with comments in the source code that > th...

...be needed to avoid recursive calls to findInheritedMethods." -- Best regards, Ivan [1] https://stat.ethz.ch/pipermail/r-package-devel/2024q3/011097.html [2] https://github.com/r-devel/r-svn/blob/776045d4601ed3ac7b8041e94c665bbfe9709191/src/library/methods/R/methodsTable.R#L457 [3] https://codeberg.org/aitap/S4_vs_onLoad

...pointers? The only >>> reference I found in the "Writing R Extensions" manual where this not >>> the case is `R_tryEval` and `R_tryEvalSilent`. >> >> Based on what I've been reading while working on (still very much >> incomplete) <https://aitap.codeberg.page/R-api>, I think that these are >> the only two cases where a SEXP can be null, precisely because a null >> pointer is distinguished from every possible value that could be >> returned by eval(). >> >> Some APIs may accept a null SEXP (with comments in the sour...

On Thu, Apr 25, 2024 at 4:24?AM Ivan Krylov via R-devel <r-devel at r-project.org> wrote: > > On Wed, 24 Apr 2024 15:31:39 -0500 (CDT) > luke-tierney--- via R-devel <r-devel at r-project.org> wrote: > > > We would be better off (in my view, not necessarily shared by others > > in R-core) if we could get to a point where: > > > > all entry points

...transfer roles without making a bunch of changes on each domain controller. It also should be fairly secure as it uses SMB. I initially was going to use the Gnome virtual file system (GVFS) but it ended up being to complex to implement in a small script. I hope this is useful for someone. https://codeberg.org/darin755/Linux-AD/src/branch/main/sysvolrepl Thank you, Darin

On Sat, 11 May 2024, Peter Langfelder wrote: > On Sat, May 11, 2024 at 9:34?AM luke-tierney--- via R-devel > <r-devel at r-project.org> wrote: >> >> On Sat, 11 May 2024, Travers Ching wrote: >> >>> The following code snippet causes R to hang. This example might be a >>> bit contrived as I was experimenting and trying to understand >>>

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

All, There seems to be a hullaboo about a vulnerability in R when deserializing untrusted data: https://hiddenlayer.com/research/r-bitrary-code-execution https://nvd.nist.gov/vuln/detail/CVE-2024-27322 https://www.kb.cert.org/vuls/id/238194 Apparently a fix was made for R 4.4.0, but I see no mention of it in the changes report: https://cloud.r-project.org/bin/windows/base/NEWS.R-4.4.0.html

...rgument and return value are both either TRUE or FALSE. Martin > [1] https://stat.ethz.ch/pipermail/r-package-devel/2024q3/011097.html > [2] https://github.com/r-devel/r-svn/blob/776045d4601ed3ac7b8041e94c665bbfe9709191/src/library/methods/R/methodsTable.R#L457 > [3] https://codeberg.org/aitap/S4_vs_onLoad