S.D.Mechveliani ([EMAIL PROTECTED]) wrote:
[ error messages printing their aguments ]
Printing the argument of a function as part of an error
message may lead to infinite error messages. It may even
lead to several calls to error which all have to be shown.
I don't think a compiler will ever be able to detect such infinite
situations and should therefore not be allowed to automatically
print arguments because the quality of the messages will be
very bad.
Also I just looked up the following in the language definition:
A call to error terminates execution of the program
and returns an appropriate error indication to the
operating system. It should also display the string in
some system-dependent manner. When undefined is used,
the error message is created by the compiler.
This suggests that a call to error should result in termination.
Perhaps I am missing something.
Regards,
Marc
