Hi Martin,
On 9/23/23 06:43, Martin Maechler wrote:
>> Hervé Pagès
>> on Fri, 22 Sep 2023 16:55:05 -0700 writes:
> > The problem is that you have things that are
> > **semantically** different but look exactly the same:
>
> > They look the same:
>
> >> x
> >
On 23/09/2023 3:41 p.m., Simone Giannerini wrote:
I know it's documented and I know there are other ways to guard
against this behaviour, once you know about this.
The point is whether it might be worth it to make NCOL and NROW return
the same value on NULL and make R more consistent/intuitive
On Sat, Sep 23, 2023 at 7:30 PM Ivan Krylov wrote:
> You're right! Looking at the code, if R_useDynamicSymbols(dll, FALSE)
> has been called for a DLL, the branch that calls dlsym() or
> GetProcAddress() to find symbols from that library by their shared
> object symbol names gets completely
Às 20:41 de 23/09/2023, Simone Giannerini escreveu:
I know it's documented and I know there are other ways to guard
against this behaviour, once you know about this.
The point is whether it might be worth it to make NCOL and NROW return
the same value on NULL and make R more consistent/intuitive
On Sat, Sep 23, 2023 at 10:00 AM Duncan Murdoch
wrote:
> I don't know the answer here, but section 6.16 of WRE suggests that you
> could explicitly make your functions visible even if they default to
> invisible.
Thanks Duncan. Unfortunately at least in my tests the visibility
settings did not
On Wed, 20 Sep 2023 12:39:50 +0200
Martin Maechler wrote:
> The problem is that some pdf *viewers*,
> notably `evince` on Fedora Linux, for several years now,
> do *not* show *some* of the UTF-8 glyphs because they do not use
> the correct fonts
One more problem that makes it nontrivial to use
This is certainly worth discussing, but there's always a heavy
burden of back-compatibility; how much better would it be for NCOL and
NROW to both return zero, vs. the amount of old code that would be broken?
Furthermore, the reason for this behaviour is justified as
consistency with the
В Thu, 21 Sep 2023 22:11:37 +
Hanyu Song пишет:
> Therefore, I am very surprised that the example below runs overtime,
> since all it has to do is to run
> reticulate::py_module_available('ctef'). If even this part is running
> overtime, I am not quite sure how to deal with it.
Can you show
I know it's documented and I know there are other ways to guard
against this behaviour, once you know about this.
The point is whether it might be worth it to make NCOL and NROW return
the same value on NULL and make R more consistent/intuitive and
possibly less error prone.
Regards,
Simone
On
В Sat, 23 Sep 2023 08:42:25 +
Ralf Stubner пишет:
> ?Random.user describes a way to hook a user- defined
> RNG into R. However, it looks like these two things are not
> compatible, i.e. `user_unif_rand` et al. are not found, if dynamic
> symbols are not allowed.
You're right! Looking at the
I am in the process of updating the rgl package. One thing I'd like to
do is to change text support in it when using OpenGL to display to be
more like the way text is drawn in WebGL displays (i.e. the ones
rglwidget() produces).
Currently in R, rgl uses the FTGL library to draw text. That
It's been documented for a long time that NCOL(NULL) is 1. What
particular problems did you have in mind? There might be other ways to
guard against them.
Duncan Murdoch
On 23/09/2023 1:43 p.m., Simone Giannerini wrote:
Dear list,
I do not know what would be the 'correct' answer to the
Dear list,
I do not know what would be the 'correct' answer to the following but
I think that they should return the same value to avoid potential
problems and hard to debug errors.
Regards,
Simone
---
> NCOL(NULL)
[1] 1
> NROW(NULL)
[1] 0
> sessionInfo()
It sounds like we need to add arguments (with sensible defaults) to complex(),
Re(), Im(), is.na.complex() etc to allow the user to specify the desired
behavior.
--
Change your thoughts and you change the world.
--Dr. Norman Vincent Peale
> On Sep 23, 2023, at 12:37 PM, Mikael Jagan wrote:
On 2023-09-23 9:43 am, Martin Maechler wrote:
Hervé Pagès
on Fri, 22 Sep 2023 16:55:05 -0700 writes:
> The problem is that you have things that are
> **semantically** different but look exactly the same:
> They look the same:
>> x
> [1] NA
>> y
>
> Hervé Pagès
> on Fri, 22 Sep 2023 16:55:05 -0700 writes:
> The problem is that you have things that are
> **semantically** different but look exactly the same:
> They look the same:
>> x
> [1] NA
>> y
> [1] NA
>> z
> [1] NA
>> is.na(x)
On 23/09/2023 4:42 a.m., Ralf Stubner wrote:
Hi everybody,
Section 5.4 of WRE suggests to use `R_useDynamicSymbols(dll, FALSE);`
when registering C/C++ routines in R packages, and Rcpp does so
automatically. ?Random.user describes a way to hook a user- defined
RNG into R. However, it looks like
On 22/09/2023 8:35 p.m., Jonathan Godfrey wrote:
Hello all,
An issue has been raised for my BrailleR package.
https://github.com/ajrgodfrey/BrailleR/issues/97#issuecomment-1732136521
I do make use of an .OnLoad() function for various tasks, including creation of
a folder to put stuff in.
Hi everybody,
Section 5.4 of WRE suggests to use `R_useDynamicSymbols(dll, FALSE);`
when registering C/C++ routines in R packages, and Rcpp does so
automatically. ?Random.user describes a way to hook a user- defined
RNG into R. However, it looks like these two things are not
compatible, i.e.
Thanks to everybody for the help and input.
I happens that Paul was already working on preparing a tinyfiledialogs
package for R !
As he seems to know what is doing much more than I do,
I will let him go ahead with the .Call version he is preparing and will
provide assistance when needed.
20 matches
Mail list logo
