![]() ![]() You see you source code and step through it, watching the program execute, line by line, and watching the values of all program variables as they change. Lastly, for program development, if you are accustomed only to Fortran for DOS then you are in for a hell of a treat. It doesn't do anything hugely useful, but it was a grat help to me in learning how to use DISLIN with SF. I give at the end of this post the source code for a program I wrote as a DISLIN learning exercise. WRITE(LUS,'('' Input file opened:''/'' '',A)') FiNAMEĬ Input filename entered but file not found and/or not openedĬ Return a request to open the same filename as an echo fileĬ Set return value of LUI to LUK because input file-not-opened THis brings up a Win Doze dilename requester dialog, in which you can enter a pathname by mouse-clicking.ĬALL DWGFIL('INPUT file name', FiNAME, '*.IN*')Ĭ No ERR, so say so and set file-opened return value of LUIĬ CALL DISP(0,FiNAME//' opened.',LEN(FiNAME)+8,0) To solve your problem with your program not finding your input files, you can use the DISLIN statements, USE DISLIN nad CALL DWGFIL, as shown below. It is given away free by the author's generosity, for non-commercial use, and it is totally superb. The source code was all F77 and SF uses F90, of which F77 works fully in its original form, as a subset with a all the F90 improvements available as if they were extensions to F77.įor (2) my GUI, I have alighted on DISLIN. I then accomplished (1) almost immediately. What Jeff done as a front end to GNU F90 and the 'Insight' debugger is exceedingly good. I had a bit of learning to do to get hang of SF. Since discovering Simply Fortran ('SF') I have set myself the task of I have a very large structural engineering project that I have been developing over many years. Because everything compiled, I suspect there is just some minor confusion with paths on the part of Simply Fortran. Please let us all know if you have more success or if things seem to remain broken. An alternative would be to open a command prompt, navigating to the directory with the exectuable, and running the compiled program manually to see if the directory error still occurs. ![]() If you're still having troubles, there could possibly be a bug in Simply Fortran. Ensure that the working directory is either blank (if your SImply Fortran version is current) or points to the directory where your exectutable and data files reside. Next, select "Launch." from the Options menu. To simplify things, first make sure that the program executable that you've compiled and your data files, "input1.txt" in this case, are in the same directory. I would guess that the error you're seeing is related to some directory confusion. To find out more, including how to control cookies, see here.If you've successfully compiled your program, it sounds like you're doing great. The construction of packages for the Package Manager is not particularly simple, hence why the Package Manager exists in the first place.Īlthough Simply Fortran 2.14 is basically ready for final testing, the actual release will be held back until the requisite packages are also upgraded. This configuration allows Approximatrix to begin updating packages as necessary while continuing to allow older installations to operate properly. ![]() If a package is made available requiring GNU Fortran 4.9 and the user still has 4.8.2 installed, the package will not even be visible in the Package Manager. Approximatrix Simply Fortran How To Handle PackagesĪn issue arises, though, when considering how to handle packages containing pre-compiled modules once the latest release of Simply Fortran is available.īehind the scenes, packages will begin shipping with required compiler versions to ensure any pre-compiled modules are compatible with the version of GNU Fortran installed. While this change is conceptually simple for most people, it presents some interesting challenges for Approximatrix.ĭuring that period, the number of packages available in the Simply Fortran Package Manager has grown considerably. This compiler release is considered a major change for Simply Fortran regardless of the numbering convention because it will once again break the compiled module format for Fortran 90 projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |