Re: GNU Classpath Linuxtag meeting minutes

[Dalibor Topic]

Andy Walter wrote:
> On Monday 14 July 2003 18:08, Per Bothner wrote:
>
> > Mark Wielaard wrote:
> >
> > > - [NotYetImplementedException]
> >
> > In the gcj list I suggested UnsupportedOperationException, with a
> > refinement:
> >
> > throw new UnsupportedOperationException (REASON);
> > where REASON is a string literal that includes "not implemented"
> > and all on a single line (to make it easy to grep for).
>
>
> What about subclassing UnsupportedOperationException like this:

> Thus, we make sure the user always receives a helpful description and it is 
> easy for VM implementations to replace the contact information by whatever 
> else. I prefer grepping for class names to grepping for strings because there 
> are no undetected typos in class names.

I agree with Andy, classes are nicer, since the compiler checks that the 
names are actually correct. But since we also talked about attracting 
new contributors on our meeting, I'd like to propose a sightly modified 
message string:

 static String nyi =
        "This method has not yet been implemented in GNU Classpath.\n\n"
        + " The GNU Classpath project would appreciate receiving"
        + " an implementation for it.\n"
        + " If you intend to contribute, please take a look at"
        + " http://www.gnu.org/software/classpath/docs/hacking.html and"
        + " get in touch with other developers on address@hidden";

I hope that we could get more contributors fixing small missing bits 
that way. I guess people who dearly want to use a missing feature 
shouldn't be that hard to convince to implement it ;)

cheers,
dalibor topic