[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: <optional> vs. <zeroOrOne>
Although I can live with both, I prefer <optional> more because... 1. TREX uses <optional>, so it's natural to use the same keyword, and I don't see any strong reason to change it. 2. One can argue that optional and zeroOrMore/oneOrMore are different things because the latter represents a repetition while the former doesn't. So keeping three names similar is a bit of over-generalization. regards, -- Kohsuke KAWAGUCHI +1 650 786 0721 Sun Microsystems kohsuke.kawaguchi@sun.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC