> Thus, if a compiler normally adds no underscore, but adds one underscore
> to symbol names containing one already, f77_underscore will have the 
> wrong value "double" and AC_F77_WRAPPERS will produce incorrect code.

You're right...  The "right" behavior at this point would be to give an
error in that case, since it is not handled by the macro, or to extend the
macro to handle it (although no known compilers actually do this).

I seem to recall posting a patch to do the former at one point a long time
ago, but there wasn't much interest at the time, in part because it
doesn't affect any known compilers...but a fix is still probably a good
idea.

Steven

Reply via email to