There seems to be a problem with Win32 API and 32-bit gfortran.

C:\gfortran\test>type hello.f90
! hello.f90

module mykinds
implicit none
integer, parameter :: ik4 = selected_int_kind(9)
integer, parameter :: ik8 = selected_int_kind(18)
end module mykinds

module Win32
use mykinds
implicit none
private

On Nov 9, 11:35 pm, "James Van Buskirk" comcast.net> wrote:

The problem is bigger than that. All Win32 API routines on 32-bit
Windows use the STDCALL calling mechanism, which has a naming
convention adding the @n at the end of the name to signify the number
of bytes to pop off the stack on return. gfortran, like most Fortran
compilers on Windows (except for CVF and MSFPS) default to the C
convention. If you call a STDCALL routine but the compiler thinks it
is a C routine, the stack gets popped twice and you corrupt the
stack. Things go downhill from there.

You will have to see what gfortran offers for specifying that an
external routine is STDCALL. Whatever it is, it's going to be an
extension and probably not part of BIND. In Intel Fortran, for
example, one uses !DEC$ ATTRIBUTES STDCALL :: routinename

Never, ever attempt to paper over the naming convention difference by
simply adding the @n suffix - the errors this will cause can be
mystifying.

Steve

On Nov 10, 7:35 am, "James Van Buskirk" comcast.net> wrote:

Call Win32 API from gfortran is possible, but for this you should
write for each used Win32 API functions interface subroutine on C.
In consequence of significant difficulties of the mixed programming
for Windows, such approach impractical. Writing of the whole program
on C will probably more simply.
Here is example such working program

---------------File myfirst1.f95------------------------------------
SUBROUTINE FortranSub()
integer i, j
CHARACTER(LEN = 15):: Text
CHARACTER(LEN = 15) :: Caption
i = 0
j = 0
Text = "Hello All"//CHAR...

alexzenk wrote:

Not an acceptable solution. A compiler targeted at a specific OS MUST
be able to directly call OS APIs. I will never ever use a compiler
which does not support this.

On Nov 9, 11:35 pm, "James Van Buskirk" comcast.net> wrote:

"Steve Lionel" intel.com> wrote in message
news:1194701088.535461.293950@22g2000hsm.googlegroups.com...

You mean kind of like

http://softwarecommunity.intel.com/isn/Community/en-US/forums/post/30242397.aspx

?

(Sorry, couldn't resist)

"e p chandler" juno.com> wrote in message
news:1194716385.730596.279790@o80g2000hse.googlegroups.com...

Well, I find the string 'WriteConsoleA' 5 times each in:

C:\g95\lib\libkernel32.a
C:\gfortran\lib\libkernel32.a
C:\gfortran\win64\x86_64-pc-mingw32\lib\libkernel32.a

so I don't think that's the problem. Doing the g95 thing with @n:

C:\g95\test>type hello.f90
! hello.f90

module mykinds
implicit none
integer, parameter :: ik4 = selected_int_kind(9)
integer, parameter :: ik8 = selected_int_kind(18)
end module mykinds

On Nov 10, 4:00 pm, "James Van Buskirk" comcast.net> wrote:

No, as a matter of fact. The post you link to relates to incorrect
name decoration for a C-convention routine, where the compiler ought
to be supplying a leading underscore but doesn't. There it's just the
name that's wrong. If you want to read an Intel forum thread that IS
relevant, see http://softwarecommunity.intel.com/isn/Community/en-US/forums/thread/30243178.as...

On Nov 10, 5:48 pm, "James Van Buskirk" comcast.net> wrote:

"Steve Lionel" intel.com> wrote in message
news:1194747615.729298.201610@v2g2000hsf.googlegroups.com...