similar to: [patch] Eliminate warnings from gcc -Wold-style-declaration

According to Writing R Extensions, the R_CallMethodDef struct has two optional fields for specifying the 'type' and 'style' (where 'style' is said to distinguish in/out/inout). But it gives no details of the possible values of 'style'. And looking in the header file Rdynload.h the definition of R_CallMethodDef does not include these two extra fields at all. (This is

I initially sent this to the biocore mailing list - but it was suggested that r-devel would also find it interesting. Many of us use a macro like #define CALL_DEF(fname, nargs) { #fname, (DL_FUNC)&fname, nargs} for use in function registration for use with .Call. For example, using the example from R Extension manual, if we want to register a C function myCall with three arguments, we

Hi, I'm trying to access the current R global environment from within C, using R_GlobalEnv. In the example below, Rgui (R 1.7.0. Win2K) crashes when I try to run assignValueToFooInR_GlobalEnv, but not when I run assignValueToFooInRhoEnv with Rho=.GlobalEnv. Can anyone tell me why? [ My motivation is that I want use defineVar to initialise a workingEnvironment (corresponding to Value

Dear list, I am trying to implement a publish-subscribe mechanism in for an embedded R interpreter. But somehow my registered closures seem to get collected by the GC, even though I have protected them. I have reducted my code to the following sample. Sorry if it is a little verbose. The first couple of call of calls still work, but at some point one of the callbacks (callback1 in my

Hello, I'm evaluating this expression expression({ for(x in 1:5){ .Call('rh_status','x') }}) a million times from a program with R embedded in it. I have attached reproducible code that crashes with Program received signal SIGSEGV, Segmentation fault. 0x00002b499ca40a6e in R_gc_internal (size_needed=0) at memory.c:1309 1309 FORWARD_NODE(R_PPStack[i]); Current language:

Hello Im new to the this stuff and have really been wanting to play but have absolutely no idea how to do this the farthest I have gotten is downloading the game onto my macbook from there website. I was hoping someone could give me a step by step asap this would much appreciated

Hello R Community, I've been working on a project that uses pre-made C++ libraries (using STL) in R and build a package. However, I've been getting an unusual segfault that I'm unable to trace its origin. After many attempts of debugging using gdb, commenting out parts (or all of my code) and valgrind, I'm unable to make heads or tails about what I'm doing wrong. In fact, when

Anton, With regard to the gfortran test cases which don't fail on x86_64 Linux, these are the exact gfortran.log entries for them under i686 Darwin9... > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (internal compiler error) > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (test for excess errors) Executing on host:

Hi, I'm a new list member, I?m a not an English native speaking (so, please forgive any error you can find in this mail) and I'm trying to install Dovecot in Debian Woody. I've installed the Dovecot package from backports and I?m trying to configure it to get the credential authentication from an LDAP backend. This is the configuration process summary I?ve done; if you need some

Hi, I'm trying to register my native routines using R_registerRoutines (...). I can compile the code, but the loader cannot resolve the symbol: undefined symbol: _Z18R_registerRoutinesP8_DllInfoPK12R_CMethodDefPK15R_CallMethodDefS3_S6 _ $ nm bgx.Rcheck/bgx/libs/bgx.so | grep R_registerRoutines U _Z18R_registerRoutinesP8_DllInfoPK12R_CMethodDefPK15R_CallMethodDefS3_S6

AFAICs Simo's patch for bug 5535 was only applied to the 3.3 series. Does the closing comment in https://bugzilla.samba.org/show_bug.cgi?id=5535 mean that the inconsistencies about RID calculation won't be addressed in the 3.0 and 3.2 series? Does the fact that 3.3.2 always uses sambaNextRid mean that algorithmic RID allocation is doomed to obsolescence? Regards, Thierry

Dear all, We are excited to announce that the our CELLAR working group charter for the standardization of FFV1, Matroska, and FLAC has been made available for external review. What this means is that it is now under review and available for comment to the wider IETF community. Please send any comments you might have(including statement of support)to the IESG mailing list by November 9, 2015.

With the obsolescence of NetBIOS, maybe it's time, for the sake of clarity and precision, to introduce a synonym like "short host name" to the "netbios name" parameter, which would eventually be phased out in the future. As it is now, the "netbios name" parameter is the only way to refer to the short form of the host name, which doesn't seem to be very

Full_Name: Steven L. Scott Version: 2.2.1 OS: Windows-Cygwin Submission from: (NULL) (128.125.60.50) I've had problems unpacking the R source coded downloaded from http://lib.stat.cmu.edu/R/CRAN/src/base/R-2/R-2.2.1.tar.gz Version info for tar and gunzip provided below (GNU legalese edited out), along with the error messages I get. Thanks. Steve /notcygwin[506] gunzip --version gunzip

There appear to be three acts_as_taggable implementations and I''m looking for a recommendation on which to use. - Gem - DHH plugin - Dema mixin The Gem implementation appears to be obsolescent, from what I can read on the lists and Google search. I like that the DHH plugin uses polymorphic associations because there will be lots of different taggable items in my application; however,

On 03/11/03 00:25, Mark Spencer wrote: > As a side note, I strongly would like to see someone implement a > client using libiax2 which implements IAX2 instead of the (now > obsolescent) IAX version 1. I'm implementing a Java-based IVR server (and yes, I know Asterisk does IVR, and no, it's not flexible enough to do what I want and no, it doesn't integrate well with the Java

Bugs compiling R-1.7.1 with Intel compilers icc and ifc, on x86-computer (Pentium IV) and linux operating system Hello, as there aren't many reports about that issue, I'll give a little report here. (Hope I don't bother anyone) The best thing about using icc and ifc are the warnings, because it is said that the Intel compilers are stricter and give more precise warnings than gcc.

Hi, Following on from suggestions made last week, I decided to install R 2.1.0 on my Linux machine. I'm running into a problem there however, as shown: make[1]: Entering directory `/d0/home/fgibbons/tmp/R2.1.0/R-2.1.0/src/library/Recommended' make[2]: Entering directory `/d0/home/fgibbons/tmp/R2.1.0/R-2.1.0/src/library/Recommended' begin installing recommended package VR WARNING:

On 2 September 2016 at 14:54, Thomas Petzoldt wrote: | Hi, | | I have the same problem and, at a first look, the issues reported by the | CRAN checks seemed easy to fix. However, after checking it again locally | and on http://win-builder.r-project.org it appeared that GCC 4.9.3 | (Windows, Rtools 3.4), same also on win-builder reports even more | issues, especially legacy Fortran (mainly

Hi Dmitry, Where were you expecting notice to have been given? If I recall correctly, the obsolescence of the C backend was mentioned many times on this mailing list, and as Owen notes, in the release notes since 2.8. I'm not trying to be snarky. You were obviously genuinely surprised by its removal, and that makes me wonder if where the core open source devs are expecting people to look for