Hi Ian,
On 04/02/2009, at 7:32 PM, Ian Rogers wrote:
> My concern is less about that we'll have something that works and more
> that we've regressed in a number of areas that I have spent time and
> effort improving. In particular to make the threading model
> intelligible. I think with a "quality review" the state of the code in
> the PNT branch could be significantly improved.
I think everyone agrees that the more intelligible the code the
better. Renaming methods and abstractions that are confusingly named
is a good idea.
> We can lose misleading
> concepts like "nicely" and "dangerously" and get back to describing
> methods for what they do. We can also decrease the visibility of
> fields (good practice and better encapsulation).
There's not much disagreement about this. We discussed some of these
specifically over lunch today. Choosing the "right" name can be
troublesome. Having identified the right name, actually changing the
code is trivial. The semantics involved are similar to those
described by the (un)interruptible / (un)preemptible annotations, so I
think the plan was to re-name the methods along those lines.
However, even those names a lot of people (me :-) don't find specially
intuitive (but then again, I don't have better suggestions).
So I don't think you need be concerned. Getting these things right
is important and the more eyes that look over it, the better.
--Steve
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-
http://p.sf.net/sfu/adobe-com_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core