Thomas E Enebo wrote:
Yeah in that case it does seem to make sense...how about modifying
things like so:
1. normal Java name
2. ruby name with underscores
IF PROPERTY {
3. java property name (minus get/set/is)
4. java property name with ? if boolean
5. ruby property name (java prop name with underscores)
6. ruby property name with ? if boolean
} ELSE {
7. java name with ? if boolean
8. ruby name with ? if boolean
}
Yeah, I like this. I can't imagine people are going to want both the
property names, original names, AND question-marked original names. I
will also formalize the same set of rules in JavaClass's method-aliasing
logic.
I'm open for other ideas on the search issue too. But I'm skeptical as to
whether it's going to be a real hit. It will only ever happen once per
method per new interface impl class.
Right now in Rails whenever we call a base method we do quite a number
of hash misses and one hash hit. So in many regards we can probably
consider the cost by looking a ruby dispatch cache misses.
True, and I keep forgetting that this will be a continual perf hit for
interfaces implemented with method_missing. Grr. I guess I just need to
come up with some benchmarks to measure it.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
