From bhh @end|ng |rom x@4@||@n|  Sat May  4 16:49:20 2019
From: bhh @end|ng |rom x@4@||@n| (Berend Hasselman)
Date: Sat, 4 May 2019 16:49:20 +0200
Subject: [Rd] R problems with lapack with gfortran
In-Reply-To: <2e68f333-1d10-02d4-3560-4b1b9d773a52@tkoenig.net>
References: <ff60d7f9-e54d-473a-bc85-7989abc887da@tkoenig.net>
 <b24b0ef5-1f45-1a03-4153-f335e4f1f8a5@gmail.com>
 <2e68f333-1d10-02d4-3560-4b1b9d773a52@tkoenig.net>
Message-ID: <6E812A6F-91B2-4412-A536-2CD672C5F4BA@xs4all.nl>

Hi, Thomas, Tomas,

Doesn't this issue demonstrate the warning and advice given in the  last paragraph of section 6.6 
of the "Writing R Extensions" manual:

<ref>
Passing character strings from C to Fortran or vice versa is not portable (and to Fortran 90 or later is even less so). We have found that it helps to ensure that a C string to be passed is followed by several nuls (and not just the one needed as a C terminator). But for maximal portability character strings in Fortran should be avoided.
</ref>

Avoid.

Berend

> On 3 May 2019, at 19:25, Thomas K?nig <tk at tkoenig.net> wrote:
> 
> Hi Tomas,
> 
> thanks a lot for your analysis.  I have created
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329
> for this, and put you in CC (if your e-mail address
> for GCC bugzilla is still current).
> 
> Regards
> 
> 	Thomas
> 
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel



[Rd] R problems with lapack with gfortran
Berend Hasselman