error.f90 standard output across machines

[nshaffer]

On my OS X machine, the throw and warn subroutines behave differently as on my #! machine when printing to stdout. On #!, the error message prints to the screen. On OS X, the message is not printed, and the program hangs. Printing to non-stdout files seems to work, though.

[nshaffer]

Huh, sometimes it works, though?

[nshaffer]

Consider a function whose results is in a PRINT *, statement. If that function uses throw/warn, then the program will be trying to recursively write to stdout.

[nshaffer]

Since this is machine-dependent, it's still a problem. If possible, I'd like to be able to report errors within a function call and have them print without having to bring the error outside the function. Perhaps the answer is in RETURN?