FTN95 beta testing

The latest FTN95 and DLLs are available for beta testing via the following download link. This is for users who have v8.30 and want to test the latest fixes. The demo has not changed. It should be extracted to its own folder.

Please be careful to create backup versions and make sure that each file is copied to the relevant installation folder.

https://www.dropbox.com/s/eosju489vghv4i7/Beta169.zip?dl=0

Paul,

I see few bugs fixed, DEC style parameters, for example, work OK, 'framed' size can be changed etc. Was no time to check if '/TABS 6' makes tabs 6 spaces like with gFortran, and numerous nice new options like 'top_or_left', AUTO_SCALE_FONT@ etc

This respond better fits Clearwin+ section... major is that finally LOG_LOG plot works reasonably, which is big deal: numbering is better aligned, axis numbering is correct. Need just few last tunings:

1. resizing plot with mouse works now OK but ultimately decreasing plot to zero size causes crash.

2. not clear how to change %PL 'title' size/font only keeping all other fonts and sizes on axis intact, i get error 'winop_hdl@ is missing'

3. simpleplot_update@ still crashes my code, I do not know where conflict is, is it with my log_linear plot or data, but I am close to prepare much smaller size demo.

4. one small issue with length of tics: when you change its length %pl[tick_len=val] the minor tics in LOG scales are the same size, not changed, but they have also change and be approximately 0.6-0.7 of length of major tics (i intentionally made them larger below)

5. little bit a problem with alighning relative axis appears for the 10**n style log axis numbering if exponent value n varies in broad range from, say, zero to 20-30. It is good or much better now if n had the same number of digits. 6)frame line width now can be changed but as a matter of discussion how about making it automatically the same size as axis_pen by default? Now default is 1pixel. This will cover 99.999% of need of changing frame_pen because typically if you need thicker axis you need similarly thicker frame. The same depth sizes for axis and frame was a default in initial stages of native PL, to me it was enough, but then frame default was changed to 1 pixel. You can use my demo as an example, with the temporally commented line 'CALL winop_hdl@('%pl[title_hfont]',hTitleFont)' it does not work

   use clrwin 
   parameter (N=5) 
   real*8 X(N), Y(N) 
   integer (7) ititle_hfont
   
   Data X/1e1, 1e2, 1e3,  1e4, 1e5/ 
   Data Y/2.2, 66, 8e10, 1111, 777/ 
   
   i=winio@('%sf%ts%bf%gf%es&', 3d0, ititle_hfont) 
   

   ! CALL winop_hdl@('%pl[title_hfont]',hTitleFont) call winop@('%pl[title='Log-Log Plot']')

   CALL winop@('%pl[tick_len=25]')
   i=winio@('%sf%ts%bf%es&', 2d0) 
   call winop@('%pl[axes_pen=2,frame_pen=2,width=2,x_axis='X (m)',y_axis='Y (rel.un.)']')  
   i=winio@('%ww%pv%pl[native,framed,x_array,scale=log_log,N_GRAPHS=1]', 625,500, n, X, Y)  
   end
   

Thanks Paul, and this is a release with an impressive number of bugs removed. I went back to a number of my bug reports and tried the beta compiler on the test codes in them. Here is a list that other users may find useful.

Fixed in 8.3.169:

https://forums.silverfrost.com/Forum/Topic/2737 (Format string with long Hollerith strings) https://forums.silverfrost.com/Forum/Topic/3301 (False error: uninitialised argument to routine) https://forums.silverfrost.com/Forum/Topic/3315 (Compiler insists on type declaration for subprogram name) https://forums.silverfrost.com/Forum/Topic/3320 (False error: assigned go to variable not integer) https://forums.silverfrost.com/Forum/Topic/3339 (With /opt /64, fails on code with namelist) https://forums.silverfrost.com/Forum/Topic/3340 (/check causes program run 800 times slower) https://forums.silverfrost.com/Forum/Topic/3348 (namelist input causes access violation in RNML__) https://forums.silverfrost.com/Forum/Topic/3350 (ishft, Rudnei) https://forums.silverfrost.com/Forum/Topic/3369 (Winio@ adjusts ESP incorrectly, Wahorger) https://forums.silverfrost.com/Forum/Topic/3372 (substring of element of string array in I/O list)

Still Open:

https://forums.silverfrost.com/Forum/Topic/3300 (compiler remembers more than it should, gets scope wrong) https://forums.silverfrost.com/Forum/Topic/3332 (local allocatable array initial status set to ALLOCATED when subprogram ENTRY is called) https://forums.silverfrost.com/Forum/Topic/3342 (SDBG64 does not show correct information on array argument)

Paul, Major of course is the crash of simpleplot_update@ which looks like due to some internal corruption of plotting engine which violates array boundaries. Working several weeks already to make the test demo for it.

John, I am curious...exactly what you have just described was before this latest update...

Use latest code above, i made small change

1. increasing one point of Y from 8333 to 8e10 to show that exponents hit the axis and
2. increased major tics (they look ugly now but do not look at this fact for a moment) to hit the numbers while minor ones do not grow and numbers do not move to the left

I have restarted this thread in order to shift the focus from Dan and John's concerns about %pl...

http://forums.silverfrost.com/viewtopic.php?p=24863#24863

John, Unless someone will confirm your plot (you still took my source before I made edition to emphasize my points above) seems you need to reinstall FTN95 and the update. All defects you show I see as being fixed.

As to Clearwin+, my opinion voiced here many times is that for well being of this compiler and even Fortran as a language in general the utilities like Clearwin+ and OpenGL made as ultimately user-friendly as in Matlab is more important then development of just the Fortran as a FORmula TRANslation language. Surprise, but the CWP is more important then the pure FTN95.

The proof is elementary: the users base of Matlab is 100x larger then combined one of all Fortran varieties. Among younger generation this factor might be even higher. And the difference between Matlab and Fortran is ? Professional integrated graphics at ultimate simplicity done in one line! And additional 10% gives integrated math libraries and 1% cooler look. This 1% percent by the way brings the same amount of users as all Fortran have.

Additionally for the FTN95 in particular as a FORmula TRANslation language the important would be future support of multithreading in OpenMP and MPI forms and ability to autoparallelize and debug multithreaded programs. Second major thing was 64bit support and it is basically now almost done.

Quoted from John-Silver Dan ... I DID use the code above !!!!

John, I think that there is something mixed up regarding which file you used to produce the plot and which compiler version you used. Add to that the chances for more error that producing images, uploading them to a cloud server and including the URL in your post.

Here is what I find. FTN95 Version 8.1 does not produce a plot, giving instead an error message, 'frame_pen= is an invalid %PL option'.

The plot that you showed does not correspond to the plotted point coordinates. For example, the peak Y-value is given in the program source as 8E10, but your plot shows about 8E4.

When you compile and link at the command line, the compiler and linker display their version numbers. Please check those numbers, as well.

Tried to download the beta. Dropbox says the file is not there anymore. John

There is a later version here...

https://forums.silverfrost.com/Forum/Topic/3403