On 14 March 2012 21:56, Emmanuel Bourg <ebo...@apache.org> wrote: > Le 14/03/2012 22:44, sebb a écrit : > > >> It's not possible to use null for a char value. > > > It assumed we changed the signature of the methods with java.lang.Character, > while retaining the primitive internally. But that's not possible due to the > getters.
I've just realised that the DISABLED value is actually exposed - just use a format with a disabled character and fetch it. It's not too late to change to using Character. > If possible I'd like to not expose this constant. The idea was that we start > with disabled features by default in the predefined formats, and then we > enable what's necessary. Thus we never have to disable anything. It's not possible currently to create a format with encapsulator, commentStart and escape all null, except by knowing the value of DISABLED. Maybe that's not allowed, but it's not rejected by validation, and can be created by using '\ufffe' directly. Likewise, encapsulator and escape are not mutually exclusive. Should they be? > Emmanuel Bourg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
