similar to: dyn.load() strange behavior

On second thought, there is a lot of metapramming code in Rcpp that runs before main, so I was wrong to say nothing can happen before main() is called. Strategically placed print statements may be the best strategy. On Wed, Jan 18, 2023 at 8:17 PM Dominick Samperi <djsamperi at gmail.com> wrote: > Since these ?stray threads? were appearing before I installed gdb into > Rtools42, this

FYI, one platform where I have not been able to get interactive rgl working is iOS 8. iOS 8 is supposed to support WebGL, and Javascript is enabled. On Sat, Sep 12, 2015 at 4:33 PM, Dominick Samperi <djsamperi at gmail.com> wrote: > Thanks for the pointers and the quick fix. > > Perhaps the generated HTML code should issue a > message like "Javascript load problem"

The package cxxPack builds without problems at CRAN under all OS's except Windows 64bit, and in the case of Windows 64bit there is a problem in a call to dyn.load(). This call happens while processing the package vignette, and the odd thing about this is that there are several calls to dyn.load() that work fine before the one that fails. This seems to suggest that Windows 64bit is imposing

This post asks members of the R community, users and developers, to comment on issues related to the GNU Public License and R community policies more generally. The GPL says very little about protecting the the rights of original contributors by not disseminating misleading information about them. Indeed, for pragmatic reasons it effectively assumes that original authors have no rights regarding

I wrote the Rcpp library and the RcppTemplate package to make it easier for developers to contribute packages to the R community. In addition to providing detailed documentation on package creation it provides a clean object mapping between R anc C++ that helps developers to implement packages that benefit from the performance of C++ and the flexibility of R. The package named 'Rcpp' was

Is it possible to set Windows' search path from within R, or to tell Windows how to find a DLL in some other way from R? Specifically, if a package DLL depends on another DLL the normal requirement is that the second DLL be in the search path so Windows can find it (there are other tricks, but they apply at the Windows level, not at the R level). Thanks, Dominick [[alternative HTML version

It appears that my archived packages Rcpp and RcppTemplate have been removed at CRAN, yet they appeared in the CRAN archives until recently. What is the CRAN policy on archives and removal? Thanks, Dominick [[alternative HTML version deleted]]

Hello, I am trying to call the BLAS Level1 function zdotc from R via a .C call like this: #include "R.h" #include "R_ext/BLAS.h" void testzdotc() { Rcomplex zx[3], zy[3], ret_val; zx[0].r = 1.0; zx[0].i = 0.0; zx[1].r = 2.0; zx[0].i = 0.0; zx[2].r = 3.0; zx[0].i = 0.0; zy[0].r = 1.0; zy[0].i = 0.0; zy[1].r = 2.0; zy[0].i = 0.0; zy[2].r = 3.0;

On 12/09/2015 7:37 AM, Duncan Murdoch wrote: > On 11/09/2015 10:14 PM, Dominick Samperi wrote: >> Hello, >> >> The recently created online "rgl Overview" at >> https://cran.r-project.org/web/packages/rgl/vignettes/rgl.html >> illustrates a problem that I am trying to resolve. >> >> At the bottom of each image block on that page appears the

On 1/18/23 19:41, Dominick Samperi wrote: > Thanks for the detailed feedback Tomas, > > I ran the command 'pacman -Syuu' again, just to be sure, and this time > it says "there is nothing to do." > > It appears that gdb is working. I was spooked by the diagnostics that > you say is a known (not serious) issue. > > My mistake was not setting a

Hello, When I try to install Rtools in the usual way into C:\Rtools on a new Windows 8.1 desktop it stalls near the beginning of the "Extracting files..." step. The Task Manager Status for the Setup app shows "Not responding" and it takes a long time to complete the installation, in spite of the fact that this is a fast machine (Intel i7) with 16 GB if RAM. There were no

Thanks for the detailed feedback Tomas, I ran the command 'pacman -Syuu' again, just to be sure, and this time it says "there is nothing to do." It appears that gdb is working. I was spooked by the diagnostics that you say is a known (not serious) issue. My mistake was not setting a breakpoint on main, so I confused problems with gdb with problems with the program I'm

Thanks, But this didn't work. It installs msys2 along with lots of other stuff, and gdb would not start as before (missing DLL's). Then I tried to run the command you suggested again, and there was a warning from the package manager about a cycle detected, but now gdb starts with the following messages... Traceback (most recent call last): File "<string>", ine 3, in

On 1/18/23 04:33, Dominick Samperi wrote: > Hello, > > I tried installing gdb into Rtools42 following the instructions here > https://cran.r-project.org/bin/windows/base/howto-R-4.2.html > > I ran 'pacman -Sy gdb', and the installation seemed to complete without > problems. > > But gdb could not be started because incorrect DLL versions were installed, > in

It appears that the runtime for an R script can more than double if a few references to a function foo() are replaced by more explict references of the form pkgname::foo(). The more explicit references are of course required when two loaded packages define the same function. I can understand why use of this mechanism is not free in an interpreted environment like R, but the cost seems rather

Consider the C (or C++) code called from the .Call interface: SEXP foo() { SEXP *p = PROTECT(allocVector(REALSXP, 10)); ... UNPROTECT(1); return p; } Why is there no danger that the allocated memory will be garbage collected after the UNPROTECT, but before the return of p? I have used code like this for some time and have never had a problem, but I'm not sure if/why it is guaranteed

On 1/18/23 17:39, Dominick Samperi wrote: > Thanks, > > But this didn't work. It installs msys2 along with lots of other > stuff, and gdb would not start as before (missing DLL's). > > Then I tried to run the command you suggested again, and there was a > warning from the package manager about a cycle detected, but now gdb > starts with the following messages...

Hello, After much tinkering I managed to build packages using the 64bit version of R with the help of hints from http://www.murdoch-sutherland.com/Rtools/ and http://www.stats.ox.ac.uk/~ripley/Win64/W64porting.html and R-admin Manual. But a hack was required, and this seems to be related to a comment about underscores at the end of the second reference above (but this comment is about FUTURE

The R docs say that there are two methods that the C programmer can allocate memory, one where R automatically frees the memory on return from .C/.Call, and the other where the user takes responsibility for freeing the storage. Both methods involve using R-provided functions. What happens when the user uses the standard "new" allocator? What about when a C++ application uses STL and

Hello, I submitted the package RcppTemplate to CRAN a couple of weeks ago but the Mac OS X binary has not appeared, and the person in charge of that process (Simon) suspects that the problem may be due to a "nested DESCRIPTION file" so that "Package:" becomes RcppTemplateRcppTemplate, or something like this. Can somebody explain what a nested DESCRIPTION file is so I can