Silverfrost Forums

Welcome to our forums

Are Internal Procedures implemented in .NET?

19 Jul 2008 2:27 #3488

I have 2 questions, related, in my case:

  1. Are Internal Procedures implemented in .NET? I get an error 'Cannot yet process records...' that seems to imply they are not. Is that true, or am I doing something wrong?

  2. The documentation states that assigned goto's are retained in the current version. If that is true, what is the correct syntax? Although the routines compile, run-time errors result.

In Fortran 77, you simply said:

ASSIGN 666 TO IRETURN . . . GOTO IRETURN --- this appears not to work.

19 Jul 2008 3:50 #3489

Question 2:

There's lots of archaic syntax associated with GOTO

I always got confused between assigned and computed GOTOs.

This one (computed):

GO TO (142,143,142,143,142,143), ID

depends on ID being 1..6 and not outside the range.

Last time I saw an assigned GOTO you had to give the possible labels AFTER the jump, i.e.

ASSIGN 34 to JUMP GOTO JUMP,(100,200,300)

Doing it without the list of possible statement numbers may be an extension.

You seem to be able to ASSIGN a format statement number

ASSIGN 100 to NFORM WRITE(*,NFORM) ... 100 FORMAT ('This is dreadful')

I simply love the arithmetic GOTO (there wasn't a logical GOTO on the IBM1130). Working out what it does nearly 40 years on is difficult :

IF ((ID-2)*(ID-6)) 163,162,163

IF (ID .EQ. 2 .OR. ID .EQ. 6) THEN GO TO 162 ELSE GO TO 163 ENDIF

or what about:

IF ((H+0.4)*(H-0.5)) 7,7,4

?

Eddie

21 Jul 2008 8:22 #3504

Eddie,

When I first started work, the company I joined used an IBM1130. I refused to use it and insisted on using a Prime 300, which I had been using while studying. It's amazing to think the fortran available did not support

if ( H .ge. -0.4 .and. H .le. 0.5) goto 7 (oops, I don't think lower case was available then)

All the programs were on card decks. Those who used the 1130, said they could debug their programs by the sound the disk drive (cartridge) made.

Thanks for the blast from the past.

John

Please login to reply.