@jblevins
do you think it is possible for long pages (like GFortran) to create a table of contents with links to the sections, either on the left margin like in Wikipedia or near the top of page?
This can be done at the top of the page by defining and linking to section IDs, for example on the HowTo page.
Thanks!
I am looking at the orphaned pages, and I have found this one:
https://fortranwiki.org/fortran/show/Virtual+Machining
The word Fortran appears nowhere, neither in the page nor in the three cited articles. It seems it brings nothing in the Fortran Wiki.
And a few orphaned pages could certainly be deleted.
Especially file extensions in Fortran Wiki which is a duplicate (title) of File extensions in Fortran Wiki (I have put a link to redirect the reader).
Thanks, I agree. I have deleted those pages.
Is the Wiki a suitable place for posting bug reports and work-arounds for the discontinued Absoft Fortran Compiler? Or would a webpage on my own website be better? Because of the challenge of converting legacy code, I will be using the Absoft compiler until it no longer works.
@jblevins
I have worked on decreasing the number of orphaned pages.
I have failed on citing the page ogpf: 2D, 3D plotting and animation
in the libraries page, probably because of the :
in its title?
Three pages are totally empty (for several years) and could be deleted:
- M. Soori Publications in Fortran Wiki
- computed GO TO statement is equivalent to a set of logical if statement in Fortran Wiki
- m_time in Fortran Wiki (but first see with @urbanjost)
- ISO_C_BINDING in Fortran Wiki : its title is a duplicate of iso_c_binding in Fortran Wiki
Three pages contain just one line:
- IEEE_ARITHMETIC in Fortran Wiki : its title is a duplicate of ieee_arithmetic in Fortran Wiki
- integer in Fortran Wiki
- URL in Fortran Wiki : the URL of that Chiversā book is already in the Books page.
I think each Fortran compiler deserves its own page in the Fortran Wiki. And it sounds reasonable to list there the work-arounds for bugs that will unhappily never be fixed. It is knowledge that deserves to be shared. See also the page Fortran Wiki in Fortran Wiki concerning the missions of the Wiki.
See HowTo in Fortran Wiki on how to create a new page. The Compilers in Fortran Wiki page seems the right place to create an internal link to a needed Absoft Fortran Compiler page.
Thank you. Will proceed with an Absoft compiler page.
I have found other pages where there are \\
instead of \
in other situations. I have fixed some of them, but there are still pages to inspect: Search results for "\\\\" in Fortran Wiki
They should be inspected one by one, those backslash having different meanings in different situations or languages. For example, it can be a \
in a Windows path. Or in a regex we can have one backslash to escape a character or two backslashes to obtain the \
characterā¦ So we have to decide carefully in each case if one or two backslash are needed.
Iām sure thatās the issue. I have renamed the page to ogpf.
I have removed all of these, thanks again.
Thanks a lot!
I have added an internal link to ogpf in two pages (libraries).
The reasons why your code does not work with gfortran, Intel Fortran, and other compilers may be of interest the developers of those compilers.