forums.silverfrost.com
Welcome to the Silverfrost forums

 How program knows that it is 64bit or 32bit? Goto page Previous  1, 2
Author Message
JohnCampbell

Joined: 16 Feb 2006
Posts: 2115
Location: Sydney

 Posted: Thu May 23, 2019 1:10 pm    Post subject: mecej4, I have been requesting for a few of these new system routines for a while, see: http://forums.silverfrost.com/viewtopic.php?t=2176&postdays=0&postorder=asc&start=120 A few more requesting some of these utility routines may help identify those that are more useful. Support for a FTN95 version of the module ISO_FORTRAN_ENV could also be helpful, which would provide some guidance for making code more portable. The idea of more flexibility on KIND values could also help. More consensus on this idea could lead to a better approach. John
PaulLaidler

Joined: 21 Feb 2005
Posts: 6004
Location: Salford, UK

 Posted: Thu May 23, 2019 3:44 pm    Post subject: It turns out that the version number is intended to be provided via _SAL_VER but this seems to have been forgotten and not updated from 450 which presumably refers to FTN95 v4.50. We can add a new macro (say _FTN95_VER) and aim to keep it up to date. I have made a note of the request for COMPILE_VERSION() etc.
JohnCampbell

Joined: 16 Feb 2006
Posts: 2115
Location: Sydney

Posted: Fri May 24, 2019 8:03 am    Post subject:

I have my own solution for compiler_version , which is:
 Code: subroutine get_compiler_version ( version )       character version*(*)       character ftn95_ver*80 !       include       version = ftn95_ver    end subroutine get_compiler_version

The include file in C:\Program Files (x86)\Silverfrost\ftn95\include looks like
 Code: ftn95_ver = '[FTN95/x64 Ver. 8.40.0 Nov18 Copyright (c) Silverfrost Ltd 1993-2018]'

It would be good if a similar (or different) approach could be applied to salflibc.dll or where suitable.
PaulLaidler

Joined: 21 Feb 2005
Posts: 6004
Location: Salford, UK

 Posted: Fri May 24, 2019 8:43 am    Post subject: For future releases of FTN95, _SAL_VER will be kept up to date and _FTN95_VER will be provided as an alternative.
DietmarSiepmann

Joined: 03 Jun 2013
Posts: 179

 Posted: Fri May 24, 2019 11:05 am    Post subject: Thanks Paul, John and mecej4 for your information/discussion (@Paul ... and for providing the symbols John, did you create include file ftn95_ver.ins? I could not find it in my SALFORD installations. Regards, Dietmar
JohnCampbell

Joined: 16 Feb 2006
Posts: 2115
Location: Sydney

 Posted: Fri May 24, 2019 11:14 am    Post subject: Dietmar, Yes, for each new version I create the file, by running ftn95 > zz, editing zz then copying into ...ftn95..\include\ftn95_ver.ins With difficulty, as you need to copy as administrator. C:\Program Files (x86)\Silverfrost\ftn95\include is now too protected.
 Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First
 All times are GMT + 1 HourGoto page Previous  1, 2 Page 2 of 2