In the first case, we can say there is some incoherence, since you find both "substring" and "subList". Thus, the second one, is perhaps a better guide to making a decision here. Thus, I would say, one might go with how the names translate into Java convention (= subarray.)
It would be good to have others' comments on this too.
Ashwin
----- Original Message -----
I changed this based on subList() in the collections API. substring() is an alternative precedent, so I am open to opinions.
Stephen
----- Original Message ----- From: "Ash .." <[EMAIL PROTECTED]>
Thanks for integrating the subarray implementation patch.
However, I am curious to know why Stephen chose to name the method "subArray", in place of "subarray". In the English language, the prefix "sub" in this sense is joined to the word with the resultant word being a single "token": subunit, subclass, suburbs, subway... substring, subarray, whereby, as per standard Java conventions, the name ought to be "subarray" rather than "subArray". Even names in Standard API reflect this: substring, etc.
thanks, Ashwin
_________________________________________________________________ Hotmail messages direct to your mobile phone http://www.msn.co.uk/msnmobile
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
