![](https://secure.gravatar.com/avatar/36f8c662be54be9df5f17def1e35d47e.jpg?s=120&d=mm&r=g)
22 Aug
2016
22 Aug
'16
4:50 p.m.
What about an UNSUPPORTED-FUNCTIONALITY ERROR subclass? I was thinking of putting it in UIOP, and exported, for the use of cases where a particular implementation doesn't support an operation. This might make it much easier to handle implementations that don't support all operations, PARTICULARLY in test cases. Best, r