search for: fortan

....4 As you can see, each datum gets imported into a separate column, whereas I'd like to have everything stored under V1. I'm also unsure as to what the error message means. Thanks in advance for your help! L?a -- View this message in context: http://r.789695.n4.nabble.com/Importing-from-Fortan-tp3889947p3889947.html Sent from the R help mailing list archive at Nabble.com.

Dear UseRs, How can i connect my FTN95 fortran compiler with R in window 7?Thanks in Advance, Elisa [[alternative HTML version deleted]]

Is it possible in R to call a fortran routine that sets variables in a common block and expect the values to persist when a call is made from R to a second routine that uses the common block? If not (as I suspect), is it possible to use a common block in a group of routines that are used together, for as long the routines do not return to R? Paul

...of the original program, or use a Just-In-Time compiler to interpret the program on a variety of platforms. To claim FORTRAN is mature is an understatement. In use for over 50 years, FORTRAN is utilized in a wide variety of legacy code bases. While younger and flashier languages get all the press, FORTAN still enjoys wide usage in many scientific fields and other businesses—especially when legacy code is involved. The implementation of a FORTAN front end would benefit both the FORTRAN user-base and the LLMV project. The scientific uses of FORTRAN—along with its other applications—are often heavily...

Getting the front end for Fortran finished is definitely something I would be interested in working on. I will draft up a little proposal and send it out to this list. -Scott On 3/19/07, Kenneth Hoste <kenneth.hoste at ugent.be> wrote: > Hi Scott, > > On 18 Mar 2007, at 04:22, Scott Fortmann-Roe wrote: > > > Hi, > > > > I noticed that LLVM had signed up as a

...on Fortran compiler long, long ago in a former life. There is no way you're going to write a usable front-end from scratch in a few months, even with the head start of a parser. The parser is the easy bit. Also -- and I'm surprised no one else noticed this -- you misspell FORTRAN as FORTAN as often as not. That does not make a good impression :) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070320/f5d408f3/attachment.html>

Hi Scott, I'm currently porting the Ada gcc front-end to LLVM. This is similar to what you want to do, so here are some comments from the trenches... > I plan on first attempting to implement the FORTRAN front-end by > co-opting the GCC FORTRAN parser. Good plan. However the Fortran front-end that comes with gcc 4.0 is known to be weak (llvm-gcc is based on gcc 4.0). That's

Hello! I am creating a packege and I would like to inclued some Fortrun subrutines. I have two questions. 1. Can I use "free form fortan" - compiles well usinf g77 -ffree-form. 2. Is it enough to place the ".for" files in scr folder? Thank you in advance for any help! Ales Ziberna P.S.: I am runing R 2.1.1 on Win XP, SP2. I installed rtools, mingw, perl as suggested in the manuals. Here are some detailsabour R: pla...

...nique predictor values and 6 significant digits setting for the smooth.spline rounds them off. Is there any way of increasing the significant digits withour recompiling a lot if code (simple editing and tham sourcing of "smooth.spline.r" function does not work, probably due to presence of Fortan functional calls)? Thank you very much in advance Sergii R version 2.9.1 (2009-06-26) x86_64-redhat-linux-gnu locale: LC_CTYPE=en_GB.UTF-8;LC_NUMERIC=C;LC_TIME=en_GB.UTF-8;LC_COLLATE=en_GB.U TF-8;LC_MONETARY=C;LC_MESSAGES=en_GB.UTF-8;LC_PAPER=en_GB.UTF-8;LC_NAME= C;LC_ADDRESS=C;LC_TELE...

Now I try to add some C and Fortan code to my package, so the NAMESPACE file is useDynLib(eha) importFrom(survival, Surv) export(mlreg.fit, risksets) but I get ..... * checking R files for library.dynam ... OK * checking S3 generic/method consistency ... WARNING Error in .try_quietly({ : Error in library(package, lib.loc = lib.l...

...'re running this on a sparc machine. The > logic seems to work okay on Linux but it uses bash. Probably there is some > bash specific logic in the configure script that sh doesn't like. Ah.. ok. I don't think its the logic figure out how to access the f2c program, but the nag-fortan compiler. The f2c stuff has always worked, unless its changed since June. Can whoever added the nag-fortran checks please fix this? I tried using bash instead of sh, and that worked so I can continue testing. Thanks. -Tanya

...go in a > former life. There is no way you're going to write a usable front- > end from scratch in a few months, even with the head start of a > parser. The parser is the easy bit. > > Also -- and I'm surprised no one else noticed this -- you misspell > FORTRAN as FORTAN as often as not. That does not make a good > impression :) I don't think he's saying he'll build that Fortran front-end from scratch, but will use an ANTLR-based parser for the front-end if the GCC parser causes problems.. Or am I mistaking? And yes, fix the FORTAN typos :-)...

...y main to link with Fortran 77 libraries... none checking for Fortran 77 name-mangling scheme... lower case, underscore, no extra underscore checking whether f77 appends underscores to external names... yes checking whether mixed C/Fortran code can be run... configure: WARNING: cannot run mixed C/Fortan code configure: error: Maybe check LDFLAGS for paths to Fortran libraries? I have tried to set LDFLAGS to different values but with no success. I have looked in the archives but found no solution. Is there a problem with the Solaris compilers? (Others seem to have rather used GCC under Solaris...

..._all_ | > packages so I am not sure we should force _all_ packages to be rebuilt. | > | > Can we not find the ones that use .C and .Fortran ? | | I do not understand how the use of r-api-x works, but my feeling is that it | will not allow to differentiate between packages using .C and .Fortan and the | rest. Right. And therefore cast too wide a net. | I am surprised that I did not see a related bug report in the Debian BTS yet, | did I overlook something? I only looked for r-base. They may not know yet. I should write to debian-devel. Any debian-med or debian-science readers here...

...main to link with Fortran libraries... none checking for Fortran name-mangling scheme... lower case, underscore, extra underscore checking whether g77 appends underscores to external names... yes checking whether mixed C/Fortran code can be run... configure: WARNING: cannot run mixed C/Fortan code configure: error: Maybe check LDFLAGS for paths to Fortran libraries? I'm having trouble deciphering what exactly the configure script is testing at that point. Based upon the message it emitted last it looks like it's trying to link conftestf.o and conftest.o (around line 25747)...

...cran? 2) Are the patches to g77 and ld still relevant? 3) what issues are we likely to encounter -- code incompatibility, ??? -- changing from 3.4.2 to the current compiler tools? As a more specific example, a particular Bioconductor package depends on the cran package odesolve; odesolve has Fortan source files. Example R code in the Bioconductor package evaluates without issues when the .zip file from cran is used, but generates warnings (originating from the Fortran code of odesolve) when compiled locally: Warning: intdy-- t (=r1) illegal Warning: t not in interval tcur - hu (= r1) to tc...

...e from R. I've done this successfully before with C & C++ code. The Fortran wrapper subroutine which is to be called by R takes a set of input arguments & then should return an array of 2 columns & the specified number of rows. I've tested the wrapping subroutine from another Fortan main program & it does work as expected, so the Fortran works, but my problem has been with the correct syntax for retrieving the output double array from within R. The wrapping Fortran subroutine is defined; subroutine xypos_parallax_r(k,year,ra,dec,ti,t0,tE,alpha,u0,piee,pien,y) k is the...

On 27 April 2017 at 12:01, Johannes Ranke wrote: | | > so it seems to me this must affect all packages in Debian sid that were | > built before the release of R 3.4.0! | | or rather before 14 April 2017, which is when R from revision r72510 was | uploaded to sid as pre-release candidate. Another example with KernSmooth: > library(KernSmooth) KernSmooth 2.23 loaded Copyright

...appended: I'm still struggling with building on AIX. I updated my config.site to follow the suggestions from R-admin: MAIN_LDFLAGS=-Wl,brtl SHLIB_LDFLAGS=-Wl,-G This led to an error during configure: checking whether mixed C/Fortran code can be run... configure: WARNING: cannot run mixed C/Fortan code configure: error: Maybe check LDFLAGS for paths to Fortran libraries? This confused me a bit, because before adding the MAIN_LDFLAGS and SHLIB_LDFLAGS to config.site this step of configure did not show an error. When I googled this I found a previous message from last year: http://tolstoy.n...

...'t break _all_ > packages so I am not sure we should force _all_ packages to be rebuilt. > > Can we not find the ones that use .C and .Fortran ? I do not understand how the use of r-api-x works, but my feeling is that it will not allow to differentiate between packages using .C and .Fortan and the rest. I am surprised that I did not see a related bug report in the Debian BTS yet, did I overlook something? I only looked for r-base.