Re: [omr-dev] TR_Method Type enum

["Mark Stoodley" <mstoodle@xxxxxxxxxx>]

That's an unfortunate corner of our compiler
code base, reflecting some of our efforts to create CRuby, CPython, etc.
compilers using the code that ultimately became the Eclipse OMR project.

The code in OMR that's conditional upon
these checks should really move to the projects they're concerned with
(isJ9 to OpenJ9, isRuby to the Ruby OMR port, etc.), but that hasn't happened
yet so they live on. In some cases (from memory) the required refactoring
isn't trivial.

I think I can safely say we would prefer
there to be no such enum, but we don't yet live in that particular universe.
I would prefer not to add to this enum, if at all possible, and would be
willing to help brainstorm any scenario where it seems like another isX()
would be needed.

There are quite a few of these little
forehead smacks, I'm afraid (that's an apology in advance, I suppose).

Mark Stoodley		8200 Warden Avenue
Senior Software Developer		Markham, L6G 1C7
IBM Runtime Technologies		Canada
Phone:	+1-905-413-5831
e-mail:	mstoodle@xxxxxxxxxx
We cannot solve our problems with the same thinking we used when we created them - Albert Einstein

From:      
 Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx>
To:      
 omr developer discussions
<omr-dev@xxxxxxxxxxx>
Date:      
 2018/06/01 06:05 PM
Subject:    
   [omr-dev] TR_Method
Type enum
Sent by:    
   omr-dev-bounces@xxxxxxxxxxx

---

Hi,

I am puzzled by this enum - why does this exist?

Thanks and Regards
Dibyendu
_______________________________________________
omr-dev mailing list
omr-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/omr-dev