![]() ![]() PS If I get the individual user licence for Mac will I will be able to run the product on two different Macs in different locations - not at the same time of course. I presume that if I change the OPEN to something like OPEN(UNIT=12.) I'll get back to getting PRINT output at the console and WRITE output in the file? I would have tested it myself but my evaluation period is up! I just wanted to be sure before parting with money. It is specifically designed to use C shared variables in place of FORTRAN COMMON variables so that it can be used to convert Real-Time Simulation. The generated C code is designed to be human-readable and suitable for further development including linking and to create DLLs. Can you provide any more information about your problem Im sure Id be able to help. Simply Fortran fully supports the Fortran 77 standard. but I think it was 2 for the other complier). FtoCConvert converts fixed-format Fortran sources to C. Before to purchase simply FORTRAN I am checking its work with trial version. ![]() The OPEN statement is OPEN(UNIT=6.) so I'm guessing that 6 is the default output for PRINT in Simply Fortran (which to be fair is the historic default value from way back. With the Simply Fortran complier all the output (from both PRINT and WRITE) goes to the output file. I then tried runs of my own code which has both PRINT and WRITE statements - when this code was run with another compiler the output from the PRINT statements still appeared on the console, but that from the WRITE statements appeared in an output file that is specified in an OPEN statement. When I ran the simple tutorial example the message in the PRINT statement appeared in the console window as expected. There's just one little question I'd like to clarify. I've been trying out Simply Fortran on the 30 day trial - and have been impressed with it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |