Thiago H. de Paula Figueiredo wrote: > Em Fri, 15 May 2009 14:39:23 -0300, Robert Zeigler <robe...@scazdl.org> > escreveu: > >> PS: I don't see EventContext implementing Iterable<String>. It just >> doesn't make sense from a semantic POV, even it makes things a bit >> more convenient. It's also a "public" interface; it's not going to >> change anytime soon. :) > > One more reason: EventContext.get() does conversion (through > TypeCoercer) from the parameter value (a String) to any type that has a > String -> type conversion, so limiting it to be an iterable of Strings > does not make much sense. :)
I noticed that, but reckoned that if Iterable was to be implemented for any particular type, String is the most fundamental: the type coercion could always be applied on the string in the loop if wanted. But it's no biggie, just an expression that I find it rather unusual to have to use explicit loop indices in Java these days when essentially performing a foreach operation ;) Cheers, Andy -- Dr Andy Buckley Institute for Particle Physics Phenomenology Durham University 0191 3343798 | 0191 3732613 | www.insectnation.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
