Yeah, the problem is that these functions are notifying/not notifying
more than just GC. How about notifyingHandshakes?
-Filip
On 4 Apr 2009, at 08:19, Richard Jones <
R.E.Jones@...> wrote:
> How about NotifyGC and NoNotifyGC?
>
> I really do think Nicely and Dangerously are too vague, I'd much
> prefer longer names that meant something (especially using an IDE like
> Eclipse which will do the typing for me - I long ago gave up using a
> teletype which hurt my fingers typing).
>
> Of course, if you do use more expressive names, it will be important
> to ensure that the name and the function remain in step.
>
> Richard
>
> On 4 Apr 2009, at 00:05, Filip Pizlo wrote:
>
>> The native thread locking classes use terms like "nicely" and
>> "dangerously" to denote whether or not the GC is notified when the
>> given method causes the thread to block. I cannot think of better
>> terms. On the other hand, I have no strong attachment to the current
>> naming scheme. Various people have spoken up about this, but I've
>> lost track of what naming people wanted.
>>
>> So. If you think that the current naming scheme is bad, what would
>> you prefer? If I don't hear any opinions, I'll keep it as-is.
>>
>> -F
>>
>>
>>
>> ---
>> ---
>> ---
>> ---------------------------------------------------------------------
>> _______________________________________________
>> Jikesrvm-core mailing list
>>
Jikesrvm-core@...
>>
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core>
>
> ---
> ---
> ---
> ---------------------------------------------------------------------
> _______________________________________________
> Jikesrvm-core mailing list
>
Jikesrvm-core@...
>
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core------------------------------------------------------------------------------
_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core