Help with Fortran

[turtle219]

I just started learning fortran and i keep getting
"illegal continuation card ignored" on every line of code that is not a comment... HELP...
program
call ceps()
end

function ceps()
real ceps
real eps1
c
ceps=1.0e0
3 eps1=1.0e0+ceps/2.0e0
if(eps1.eq.1.0e0) return
ceps=ceps/2.0e0
goto 3
end
Thanks for any help

 

[rgwalt]

Crazy Fortran 95 stuff...

program
call ceps()
end

function ceps()
real :: ceps
real :: eps1
c #<---- Whats this?
ceps=1.0e0
3 eps1=1.0e0+ceps/2.0e0
if(eps1.eq.1.0e0) return
ceps=ceps/2.0e0
goto 3
end

Also try putting your function before your end statement, but also put a STOP statement before the function.

Ryan

 

[turtle219]

didn't help
i have to use F77, but the big problem is what the heck is "illegal continuation card"?????

 

[rgwalt]

I have no idea what that error is. If you are trying to use F77, I don't think your GOTO statement will function. I could be wrong though. Also, what is that c doing after your variable declarations?

Ryan

 

[rgwalt]

Also, you need to throw in a name for your program after the program statement.

Last but not least, you will probably want a write statement to give some output there ace.

Night man, and good luck.

Ryan

 

[EagleKeeper]

The Continuation indicates that the line of code is attempting to span more than one line.

There is a column (I think #6) that is to be kept blank (space) unless the code is an extension of the previous line.

With Fortran, I believe that all code starts in Column 7.
Reference numbers go in Cols 1-5.
Cols 73-80 can also be used for comments.

Do not take this as gospel, however I made my living in Fortran from 1970-1994.

 

[Spamela]

<< didn't help
i have to use F77, but the big problem is what the heck is "illegal continuation card"????? >>



i did fortrash back in the early 70's.
at that time you punched your program into thin paper cards that measured about 3"x8" using a typewriter-like machine
(one program line per card). then you submitted your deck of cards to the God-like creatures who protected the computer from vermin like you. then, anywhere from 30 minutes to 24 hours later you got your deck back along with a hardcopy of results of the compilation (or program execution if you were lucky).

having to iterate this process made you care about getting it right before you started typing.

 

[EagleKeeper]

Spamela

You must be getting old. You forgot about the lines of 2-10 people waiting to use the keypunch machines.

Remember number the cards so you could try to put the deck back together when you played 52 card pickup:disgust:

 

[Linflas]

If I recall from my FORTRAN 77 days the official standard was CC (Card Column) 1-5 label, CC 6 continuation character, CC 7-72 statement, CC 73-80 sequence number (drop a deck of cards once without these and you converted immediately). Make sure you are not using tabs as well.

 

[Spamela]

<< Spamela

You must be getting old. You forgot about the lines of 2-10 people waiting to use the keypunch machines.

Remember number the cards so you could try to put the deck back together when you played 52 card pickup:disgust: >>



me, old? i worked with a guy who told me about an optimization technique he used with rotating drums (used for storage). you commanded the drum to go somewhere, then your program went off & did something else while waiting for the spot on the drum to get under the read/write head, then you read/wrote your data - no stinking operating system to slow things down.

i worked with another guy who had a project on punched cards codenamed "nixon." one day he dropped his huge deck, then booted it all over the room in his attempt to grab it. someone commented that "You won't have Nixon to kick around anymore."

i forgot to mention the use & value of rubber bands for one's deck.