forums.silverfrost.com

Ralf

I have had a look at this and this feature is not currently available in ClearWin+ but could be added.

I will add this to the list as a request for a new feature.

This bug has now been fixed for the next release of FTN95.

Ralf

If you are using recent DLLs for the ClearWin+ library you will get the option to continue and ignore the error.

If you have this option and are able to continue, do tooltips appear for the ...

The internal name is __win_new_page and access could be provided via CLEARWIN.ins (or its module). It might need an alternative Fortran alias (other than NEW_PAGE@) for when DBOS.ins is used with CLEA ...

Ken

In your version CURDIR@() appears on the RHS of an assignment within the function that is currently being compiled. This is enought information for it to assume that it must be an external func ...

The compiler needs to be informed that CURDIR@ is an external function.

character*256,external::CURDIR@

SRC is an adaptation of the C++ compiler SCC so the strings are C strings and the backslash is an escape character.

Code written for a Fortran compiler uses Fortran CHARACTER variables and literal ...

I am not sure but for 64 bit applications the RESOURCES directive only works when using /LINK or /LGO on the command line.

Kenny

If you have a short working program that illustrates a false error report then please send it to us so that we can fix it.

Kenny

You could try using

/inhibit_check 1 2

on the FTN95 command line but that may not be wise.

I am not really in a position to be able to provide advice on how to debug your code.

Kenny

This works fine for me (for both 32 bits and 64 bits)...

subroutine alloc(addr, size)
integer(7)::addr,size
character,pointer::arr(:)
ALLO ...

I should have also tested the code for a 32 bit application. It works for 64 bits.

There is something wrong with addr = loc(arr). addr = loc(arr(1)) is better but still not right.

I will have to ...

Kenny:
If you send me a personal message with your email address then I will email you a copy of the code.

mecej4:
Yes ASSOCIATED is better and avoids the warning message. I will edit the post.
...

Here is some code that illustrates how to get the address of a block of memory from the global heap using a call to ALLOCATE and FTN95.

subroutine alloc(addr, size)
integer(7): ...

I have encountered a problem which means that I will not be able to provide access to the new routines described above.

At the moment the general advice is to move to 64 bits as soon as possible an ...