Hi Graeme,
There is only one function in my package that uses multiple cores:
bootSE(). However, this function is not called in any of my vignettes
because it is computationally expensive. The Rmd code has `eval = FALSE`
options for all of these cases. Therefore, I am at a loss as to why these
v
I'm not familar with fortran but the warning message is: "Found the following files with
non-portbale usage of KIND:." In "Writing R Extensions/Writing portable packages/Portable
Fortran code" it mentions the use of REAL(KIND=8) types are not portable since compilers can
map values to differen
Hi Ivan,
In my experience, if you add purl=FALSE to those chunks, it will pass the
checks. This was the default but changed/ is the default on some platforms
not others when you have error=TRUE (don't recall details).
Jisca
On Fri, 7 Jun 2024, 16:05 Tim Taylor,
wrote:
> Does this issue over i
e file src/nwout.c and the calls of various functions therein in the
other fortran files.
regards,
Berend Hasselman
On 08-05-2024, at 10:37, Jisca Huisman wrote:
Hello,
I like to use write() in Fortran code to combine text with some integers
& doubles, to pass runtime information to R in
Thanks for your help!
On Thu, 09/05/2024 06:30, Berwin A Turlach wrote:
Hi Jisca,
On Wed, 8 May 2024 10:37:28 +0200
Jisca Huisman wrote:
I like to use write() in Fortran code [...] But from 'writing R
extensions' it seems that there have been quite a few changes with
respect
Hello,
I like to use write() in Fortran code to combine text with some integers
& doubles, to pass runtime information to R in a way that is prettier
and more legible than with intpr() & dblepr(). In the past any calls to
write() were strictly forbidden in Fortran code, as apparently it messed
Kalibera wrote:
On 12/18/23 15:09, Ivan Krylov wrote:
В Mon, 18 Dec 2023 11:06:16 +0100
Jisca Huisman пишет:
I isolated the problem in a minimal working example available here:
https://github.com/JiscaH/flang_segfault_min_example . All that does
is pass a vector of length N*N back and forth be
Hello,
My package sequoia contains Fortran code, and failed to pass the
pre-test on Debian with the new flang-new compiler. I was able to
reproduce the issue, but strongly suspect it is an issue with
flang-new-17 rather than with my code. However, since in the past when I
thought the problem
