Note that Fortran 90 onward is backward compatible with Fortran 77 (only a very few minor exceptions). So... you can read/write F77 with a newer version compiler. And, the newer compilers are much more likely to find "bugs" in some of your older codes.
Dan :-)
Do you mean to delete "Duplicate" lines?
It should be very simple to do in fortran (any version from 77 to 2008). Here's a simple pseudo-code-logic:
Allocate a character string array, a(:), at lease big enough to store all lines of the file.
Read each and every line into a character...
Yes. I think it is (for whatever that is worth)!
I'm currently doing work with their 7.2 compiler. But.... their 5.6 compiler worked great for me. There isn't that much difference between them.
Dan
It's surprising that your code compiled ran at all.
You've declared three arrays, mac, mac2 and mac3 with unknown sizes. m, n & k must have actual values before you declare mac, mac2 & mac3.
Put this statement before your Double Precision line and you'll be fine:
(note: this assumes...
After the backwall shears off... the EQ continues. Thus.. the backwall essentially becomes irrelevant. Caltrans does not have a specific policy on how exactly to analyze this situation as it is very complex and even the best analytical models you might come up with are still just going to give...
Does VB work with Dos box windows? Hmmm. I know QuickBasic does (from which VB sprang).
From my past experience with QB, it is an excellent language for simple Dos screen manipulations (with color). And, since you are already a fortran programmer, picking up the little bit of QB you need...
That should be relatively straight forward in most languages. You hint that you have a fortran compiler?
Open the file.
Read each line (1 at a time) into a long character string.
Use the INDEX() function to search for "RUN" until it is found.
After finding "RUN" search the remainder of that...
A method that stores only the non-zero's has the "potential" to be much better than a bandwidth solver. It uses less memory (as long as your model is large enough) and probably has to perform fewer calculations also... which in turn means... less accumulated truncation and roundoff errors in...
Yes. I've seen plenty of codes written by language experts who can cram an amazing amount into a single line of code. I'm impressed by their capability to do that, however, attempting to understand their code or debugging it can be a nightmare.
I like to keep the code as simple as possible...
I agree 100% with hokie66. It is Highly unlikely that you want to form a plastic hinge in your pile as that essentially indicates a failure of your pile. The real question might be... at what location on each pile does the maximum moment due to the applied loadings occur and... what is the...
I don't know what Autodice is. However... as for Fortran and Excel... Opening and closing text files in Fortran is very simple. But, if you are trying to open Excel itself with a file loaded into it, that's a totally different ball game.
It should be very easy to use Fortran (most compilers...
Hi Turantug,
Something doesn't seem quite right. All Fortran compilers should allow you to declare Double Precision variables anytime you want to. If they don't, they simply aren't valid fortran compilers. And, if you are on a Windows computer, then... it is pretty much a given that your...
Sometimes it matters, sometimes it doesn't. If he is writing a program that he wishes to use for a long time... or continue to add to and maintane in the future, or in the case that he wants it to run fast ( I doubt that is the case here, but... it is certainly a concern with some codes ). C...
Here's a simple example program. It opens an input file. Reads each line of the file. Searches each line for the string, "Member Area". If it finds it, it assumes a real number is on the line after "Member Area" (nothing else on the line after that). It reads the Area value and writes it to...
As stated by others... "quad" precision is not truly defined or standard (even "double" depends on the computer system you are on). Some compilers will give you the extended precision you want easily.
What type of application do you need the extra precision for? Many times... the extended...
I've seen a fair number of people try to do fortran to C conversions. It's often not nearly as easy as originally perceived. I agree that fortran is relatively simple and if the original code is fairly simple and straight forward, a conversion is probably pretty simple. But... I've known of...
I'm a bit curious as to what possible reason there might be for suggesting that an old fortran code be converted to either C or C++ or any other language, especially, if you don't even know what the code is for?
If OldManK isn't sure what he needs to recompile the code using fortran, he...
I think you all will find that "==" is nowadays much more commonly used than ".EQ.". I'd venture that this has been true for more than 10 years now for those working with Fortran90 or beyond.
Also... the above code now works due to the use of the variable PARAM. The symbol used to check...
You need to post your actual code. You haven't given anyone nearly enough information to help you out. Though... to venture a quick GUESS, I'd say that you have not declcared the varialbe "nulchr" to be of the CHARACTER type.
Dan :-)
dan@dtware.com
