On Wed, Jun 13, 2007 at 09:37:58PM +0900, Yossef M. wrote:
I think Chad’s point stands. It seems whatever is encapsulated in the
enum’s find search code would be better off as a method on that
object. That would make the test cleaner and then there won’t be any
worry about block style precedence.
Actually, I think you assumed more meaning in what I said than I
intended. The same goes for the previous poster, too. I didn’t mean
that the precedence diference wouldn’t or shouldn’t prompt you to choose
wisely between do…end and {…} syntaxes – only that the difference
in
precedence between the two isn’t something I’d seen, or probably
should
see. I mean precedence “between the two” in the same way I’d mean it in
relation to + and * operators: when stringing things together, the
precedence of + and * in relation to one another becomes important, such
as in this case of potentially ambiguous intent:
1 + 2 * 4
