Re: [cp-patches] RFC: hacking guide - unrealistic code paths

[Meskauskas Audrius]

> I would prefer our own Error/Excpetion with preset text message.

The simpliest case is not to use the message at all, as the fact of throwing 
an exception
of such kind explains enough: something is very seriously broken.

We may, however, to have a pre-set message, suggesting to contact our team 
for support
if the problem persists and the user thinks it is really a Classpath bug.

> a subclass of InternalError might be a good start.

The InternalError or subclass of the InternalError seems a good solution for 
me, specifying
the problem more precisely than an Error. The AssertionError may also have a 
similar
meaning. The AssertionError is already included in Classpath.

Audrius