C vs. FORTRAN

[Mat Waites]

In article <5234 at ihlpf.ATT.COM> nevin1 at ihlpf.UUCP (00704a-Liber,N.J.) writes:
]
]Security in FORTRAN (with respect to calling conventions)??  Look at the
]following piece of pseudoFORTRAN:
]
]	subroutine foo(j)
]	j = 5
]	end
]	...
]	call foo(1)
]
]This passes through the compiler with no problem.  If you look at the
]run-time error, it's usually a memory violation and not a
]compiler-generated error.  Some security.
]-- 
] _ __			NEVIN J. LIBER	..!ihnp4!ihlpf!nevin1	(312) 510-6194

I have worked on several systems where the example code would run with no
problems.

No problems except that the constant "1" would have the value of 5 for
the rest of the program. This kind of problem can make for interesting
debugging sessions, especially for neo-fortranners.


Mat

-- 
 W Mat Waites            |                         |
 Emory Cardiac Data Bank | UUCP: gatech!emcard!mat |
 Atlanta, GA 30322       | PHONE: (404) 727-7197   |