harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Ellison <t.p.elli...@gmail.com>
Subject Re: [jira][general] Good issue resolution guideline update
Date Wed, 07 Feb 2007 09:30:37 GMT
Alex Blewitt wrote:
> On 07/02/07, Alexey Petrenko <alexey.a.petrenko@gmail.com> wrote:
>> 2007/2/7, Alex Blewitt <alex.blewitt@gmail.com>:
>> > On 06/02/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
>> > > The pack200 code does have to be internationalized -- why would
>> there be
>> > > an exception for that module?
>> >
>> > Mostly because it's a work-in-progress, and at present when I detect
>> > an error condition (or part of the parsing tree that I can't handle) I
>> > throw new Error("Not yet implemented"). In other words, it's a marker
>> > to let me know I need to go back there and fix it.
>> It is better to mark such methods by adding NotImplementedException to
>> throws clause. japitools will catch such methods.

Marking the methods will only be of interest to JAPI if they are JSE API
methods.  That may be worthwhile to indicate they are under development.
 There is no point in labelling the implementation methods.

> It's not methods that are unimplemented; it's certain blocks of code
> paths.

You can still throw an exception though?

> Anyway, they won't be there for long :-)

Send more code<g>


View raw message