Subject: reporting message send errors at run-time
From: Mayur Naik (mayur_naik@hotmail.com)
Date: Mon Feb 21 2000 - 05:22:02 PST
Hello!
Could you please tell me which of the following is the most suitable way to
report at *RUN-TIME* that an MSA method does not exist for a message send:
1. Report all errors by a single error method:
msg-err(msg-name n, run-time-class-arg-list l)
{
print("MSA method does not exist for message %s(%s)", n, l)
}
2. Report 'message not understood' and 'message ambiguous' errors
separately:
msg-not-understood-err(msg-name n, run-time-class-arg-list l)
{
print("message %s(%s) is not understood", n, l)
}
msg-ambiguous-err(msg-name n, run-time-class-arg-list l)
{
print("message %s(%s) is ambiguous", n, l)
}
3. Same as (2) above except that the set of applicable methods is also
passed as an argument to msg-ambiguous-err and printed.
Note that as the verbosity in error reporting increases, the efficiency of
the dispatcher decreases, since the error reporting methods themselves
become distinct targets, making the multi-way switch bigger and slower.
Thanks.
-- Mayur
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
This archive was generated by hypermail 2b25 : Tue Oct 03 2000 - 15:21:22 PDT