Hi Malte, > 1) There is IMHO a lot of API doing something like that with "0". > An Edit with max text len "0" doesn't make much sense, so 0 is fine.
"Value x has no other meaningful semantics, so let's misuse it" is no valid argument, IMO. > 2) w/o a special value, you also must introduce something like > "EnableMaxTextLen(bool)", otherwise you can't turn off max text len. Sure. But this also isn't an argument why it should not be done. > 3) For a simple Edit, you even don't need such functionality, because > there is no difference between "0" for no limit, or datatype_max_size > (string). Which is an implementation detail. The edit class could still implement "EnableMaxTextLen( FALSE )" as "ImplSetMaxTextLen( datatype_max_size )". Such implementation details, however, should not affect the API design. APIs are for being used in a clear, unambiguous way. Not necessarily for saving every small bit of in the implementation. > But I think this is a theoretical discussion, because nobody will change > the implementation (now) ;) That's true. Nonetheless, you didn't say anything which convinced me that "EnableMaxTextLen" would be bad, if we would ever embark on it. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
