View previous topic :: View next topic |
Author |
Message |
EKruck
Joined: 09 Jan 2010 Posts: 224 Location: Aalen, Germany
|
Posted: Thu Jan 19, 2017 2:24 pm Post subject: Next Release |
|
|
Is there already any preliminary expectation for a next release? |
|
Back to top |
|
|
silverfrost Site Admin
Joined: 29 Nov 2006 Posts: 191 Location: Manchester
|
Posted: Thu Jan 19, 2017 3:22 pm Post subject: |
|
|
Soon. There is quite a bit going into this release including a 64-bit check mode,64-bit optimiser and more robust 64-bit debugger, new installer and lots of 32-bit fixes. We just need to convince ourselves it is all stable and in a condition people will appreciate. |
|
Back to top |
|
|
JohnCampbell
Joined: 16 Feb 2006 Posts: 2554 Location: Sydney
|
Posted: Thu Jan 26, 2017 2:20 am Post subject: |
|
|
Paul,
With the next release, could we have a list of the status of each compiler option when used with /64 ? At least those that are not fully supported.
I tried to compile using ftn95 prog /64 /debug, hoping to get an improved traceback report on a program that was crashing, but did not get a line number output included in a traceback report.
It may have been the holiday break, but I could not make use of the addresses provided in a recent error dump, when /debug was used.
John |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Thu Jan 26, 2017 8:29 am Post subject: |
|
|
John
The intention is support all command line options except those that are explicitly trapped and give an error report.
Here is a list of the remaining options that will be excluded from the next release...
Code: | /CKC
/CLR
/DEBUG_SOURCE
/DEFREAL_KIND 3
/HARDFAIL
/P6
/STDCALL_EXPORTS
/XREAL
/MKLIB
|
|
|
Back to top |
|
|
|