Hi Alan,
yes, I will test this on Windows the coming few days.
In line with the other files of the F95 binding library
I suggest we use "sfcmd95.f90" as the new name.
Regards,
Arjen
On Fri, 27 Jan 2012 14:39:52 -0800 (PST)
"Alan W. Irwin" wrote:
> On 2012-01-27 09:56+0100 Arjen Markus wrote:
On 2012-01-27 09:56+0100 Arjen Markus wrote:
> The concise story is: these intrinsics do work from within
> a DLL or a shared object with both gfortran and Intel
> Fortran and apparently with other compilers as well.
>
> So I suggest we put an adjusted configurable.f90 into the
> library - there i
Hi Alan,
I have to correct this message:
As you can see it contains some rubbish left over from
examining a problem I had with Intel Fortran. The program
as I mailed it does not use the two intrinsics (I got an
error message about the initialisation of the runtime
library and wanted to make sure i
Hi Alan,
I tested this issue this morning with the following simple program:
--- test_arg.f90 ---
! test_arg.f90 --
! Small test program: command-line arguments reachable
! via a DLL?
!
program test_arg
use arg_mod
implicit none
call arguments
end program test_arg
---
and
Hello Alan,
On Mon, 23 Jan 2012 11:45:22 -0800 (PST)
"Alan W. Irwin" wrote:
> Hi Arjen:
>
> I just spotted something of interest in the
>gfortran-4.4.5 documentation
> with respect to command-line parsing and the Fortran
>2003 standard.
>
> To review the current status of Fortran command-li
Hi Arjen:
I just spotted something of interest in the gfortran-4.4.5 documentation
with respect to command-line parsing and the Fortran 2003 standard.
To review the current status of Fortran command-line parsing,
bindings/f95/configurable.f90 uses iargc and getarg to parse the
command line. Thes
