Skip to content

Changes in checking & error messages

1 message · John Chambers

#
Some fixes have been made to check a few errors better & to report
something like the correct error message in other cases.

- setMethod will now refuse to set a method for a primitive function for
a basic class ("[<-" for "matrix", for example).  Previously the method
was set but never dispatched.  (For a few days, the change prohibited
some valid methods for operators, with one basic operand, but that case
should be fixed now.  Thanks, Vince.)

- a number of functions such as getMethods, showMethods, etc. should
give better error messages if presented with arguments they don't
understand.  There are some additional low-level checks in various
places that should replace error messages about objects at the C level
with no slots by more comprehensible information.

Please report any glitches that seem to have been introduced.

John