similar to: Using Fortran 90 code in packages for CRAN

Hello, I work under windows xp and I am trying to build a R package with a subroutine written in fortran 90. I have installed all the updated tools and I am working with R-2.4.0 or R-2.5.0. When I check a package with a subroutine in fortran 77 (and extension f) everything is ok. When I try to build the same package with a subroutine in fortran 90 (with extension f90) the following warning

We have (spatial statistics) group here that are (about to) interface Fortran 90 and/or 95 software to R and/or S-plus. My recommendation has been against this because of non-availability of GNU or other free (not only moneywise, in the GNU sense) compilers for Fortran 9x. Does anybody have good guesses about the future here? The user group here say they like F 9[05] because of its ``object

I am reading the manual sections illustrating how to call a Fortran subroutine from R. I feel uneasy at the explicit statement about ".Fortran" interface working with Fortran 77. I would like to call a Fortran-90 subroutine from my R script. Is that supported at all ? Thank you, Maura tutti i telefonini TIM! [[alternative HTML version deleted]]

Hi! Is there any package on CRAN that uses Fortran-90/95? I would like to study it. Thanks, Gregor

Dear R-developers, in a new package, I'm currently working on, I tried to add a new method to function "t.test". The new class, on which the method is based, is called "speclib", so I defined the funcion for the new method as "t.test.speclib". R CMD check now gives always a warning, that S3 methods are not consistent, because R does not recognize that the

I have been revising some FORTRAN 77 routines in R packages I have previously submitted. Since R is now using gfortan I experimented with some Fortran 90 code (array intrinsics primarily). So far the code is still in F77 fixed format, in files suffixed .f (not .f90), but incorporates some F90 constructs. It has worked fine in linux/R. I tried to follow the thread of previous discussions

Hi, I found some bottlenecks in my R code with Rprof. First I wanted to rewrite them in C, but a colleague keeps suggesting that I learn Fortran, so maybe this is the time to do it... I like to learn new languages and do it fairly quickly. I would appreciate the advice of others about these questions: 1) I hear bad things about Fortran. Sure, F77 looks archaic, but F90/95 seems nicer. Is it

Following the setup in Prof.Duncan Murdoch's page, I have successfully compiled the DLL for one Fortran 95 program using Gfortran and got 300 times speed boost. For the second set of fortran programs, However, I have this error message R CMD SHLIB -o jiangang kdtree2.f90 jian.f90 gang.f90 m2c -o jian.o jian.mod make: m2c: Command not found make: *** [jian.o] Error 127 Can anyone

Hello, I work under windows xp and I am trying to build a R package with a subroutine written in fortran 90. I have installed all the updated tools and I am working with R-2.4.0 or R-2.5.0. When I check a package with a subroutine in fortran 77 (and extension f) everything is ok. When I try to build the same package with a subroutine in fortran 90 (with extension f90) the following warning

Hi, All, I have come across a problem building a DLL from .f90 source (R 2.3.1, Windows XP). When using the R CMD SHLIB procedure, the DLL itself was being built, but its export table was empty. Among the output from R CMD SHLIB the following message appeared: c:\mingw\bin\nm.exe: 'a.out': No such file The reason is the empty list of dependencies in the pattern rule for DLLs

Interesting problem. I'm very rusty on S4 but would one solution be to, already now, add 'simplify = TRUE' to the S4 method and document it; setMethod("apply", signature(X = "Speclib"), function(X, FUN, bySI = NULL, ..., simplify = TRUE) { ? Henrik On Fri, May 22, 2020 at 6:26

I successfully used .Fortran to load and execute my fortran procedures under WinXP and 32 bit R. Alas, the same isn't true with my next Windows 7/64 machine, R 2.14.1 (64 bit) and the gnu gfortran (64) compiler (mingw64 v. 4.6.1). Though I'm able to compile the routines from the command line using gfortran '...', .Fortran('foo2') results in an error saying the Fortran

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to add some Fortran 90 code to an existing package. When I compile and load the file manually like: SHELL> R CMD SHLIB file.f90 R> dyn.load("file.so") I can use the .Fortran() fine. However, when I try to build, install and load the library I seem to be missing something. I do a: SHELL> R CMD build dir SHELL> R

I recently developed an R package to make available a very large legacy program written in Fortran. My package has been rejected by CRAN due to this Write statement with the message "As 'Writing R Extensions' warns you against including Fortran I/O, this will not be allowed." The issue is that this Write statement does not involve I/O it is inernally writing an integer to a

I have no experience with incorporating Fortran code and am probably doing something pretty stupid. I want to use the following Fortran subroutine (not written by me) in the file SSFcoef.f subroutine SSFcoef(nmax,nu,A,nrowA,ncolA) implicit double precision(a-h,o-z) implicit integer (i-n) integer l,i,nmax double precision nu,A(0:nmax,0:nmax) A(0,0) =

I have no experience with incorporating Fortran code and am probably doing something pretty stupid. I want to use the following Fortran subroutine (not written by me) in the file SSFcoef.f subroutine SSFcoef(nmax,nu,A,nrowA,ncolA) implicit double precision(a-h,o-z) implicit integer (i-n) integer l,i,nmax double precision nu,A(0:nmax,0:nmax) A(0,0) =

I have the following FORTRAN code converted to a DLL: ! my_xmean.f90 ! ! FUNCTIONS/SUBROUTINES exported from my_function.dll: ! my_function - subroutine ! subroutine my_xmean(X,N,XMEAN) ! Expose subroutine my_function to users of this DLL ! !DEC$ ATTRIBUTES DLLEXPORT,C,REFERENCE,ALIAS:'my_xmean_'::my_xmean ! Body of my_function DOUBLE PRECISION X(N) XMEAN=0D0 DO J=1,N

Dear R Developers, the new simplify argument in apply causes that my package (hsdar) does not pass the checks in R-devel. The workaround, Kurt Hornik send me, is working for the R-code: if("simplify" %in% names(formals(base::apply))) do something else do something else Unfortunately, I cannot conditionalize the man pages of the functions. I get the message that

Dear R community, I have a question on how R manages memory allocation in .Fortran() calls under Windows. In brief, apparently, it is not possible to allocate large matrices inside a Fortran subroutine unless you pass them as arguments. If you do not act in this way RGUI crashes with a stack overflow error and acting on memory through vsize nsize ppsize and memory.limit does not help at all.

Hello all, I would like to read the specific line number row of a direct access file (which is stored as a n_row*n_col matrix of elements kind=p) without reading all the preceding lines (i.e 1,2,..,row-1). Is there a function in R that can perform this task? To solve my issue, I tried without to call Fortran from R by doing the following steps: I) I wrote a subroutine in fortran called