>
>
>
> >>> That is not true at all - the presence of header does not constitute
> >> declaration of something as the R API. There are cases where internal
> >> functions are in the headers for historical or other reasons since the
> >> headers are used both for the internal implementation and pack
> And in general, I'd urge R Core to make an explicit list of functions that
you consider to be part of the exported API
While I believe R Core is in the process of such clarification, I'd also
vote for this. Now that WRE has "experimental" category, and if we take the
current definition of "docum
A few more thoughts based on a simple question: how do you determine the
length of a vector?
Rf_length() is used in example code in R-exts, but I don't think it's
formally documented anywhere (although it's possible I missed it). Is using
in an example sufficient to consider a function to be part
> On Apr 25, 2024, at 12:55 AM, Hadley Wickham wrote:
>
>
>
> >>> That is not true at all - the presence of header does not constitute
> >> declaration of something as the R API. There are cases where internal
> >> functions are in the headers for historical or other reasons since the
> >> h
On Wed, 24 Apr 2024, Hadley Wickham wrote:
That is not true at all - the presence of header does not constitute
declaration of something as the R API. There are cases where internal
functions are in the headers for historical or other reasons since the
headers are used both for the internal
Hi Kurt,
Is it intended that numeric_version() returns an error by default on
non-character input in R 4.4.0? It seems that I can turn this into a
warning by setting
_R_CHECK_STOP_ON_INVALID_NUMERIC_VERSION_INPUTS_=false but I don't seem
to be able to find any of this mentioned in the NEWS fil
On Wed, Apr 24, 2024 at 1:32 PM luke-tierney--- via R-devel
wrote:
>
> On Wed, 24 Apr 2024, Hadley Wickham wrote:
>
> >>
> >>
> >>
> > That is not true at all - the presence of header does not constitute
> declaration of something as the R API. There are cases where internal
> functi
I'm using bleeding-edge R-devel, so maybe my build is weird. Can
anyone else reproduce this?
View() seems to crash on just about anything.
View(1:3)
*** stack smashing detected ***: terminated
Aborted (core dumped)
If I debug(View) I get to the last line of code with nothing
obviously l
As suggested by Josh Ulrich, here's what I get when running under
valgrind.
$ R -d valgrind
==218120== Memcheck, a memory error detector
==218120== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==218120== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright
info
==2
On Wed, 24 Apr 2024, Hadley Wickham wrote:
A few more thoughts based on a simple question: how do you determine the
length of a vector?
Rf_length() is used in example code in R-exts, but I don't think it's
formally documented anywhere (although it's possible I missed it). Is using
in an example
> Hervé Pagès writes:
> Hi Kurt,
> Is it intended that numeric_version() returns an error by default on
> non-character input in R 4.4.0?
Dear Herve, yes, that's the intention.
> It seems that I can turn this into a warning by setting
> _R_CHECK_STOP_ON_INVALID_NUMERIC_VERSION_INPUTS_=false
On Wed, 24 Apr 2024 19:35:42 -0400
Ben Bolker wrote:
> I'm using bleeding-edge R-devel, so maybe my build is weird. Can
> anyone else reproduce this?
>
>View() seems to crash on just about anything.
Not for me, sorry.
If you have a sufficiently new processor, you can use `rr` [*] to
capt
12 matches
Mail list logo
