[Zope3-dev] Voting on Schema design

[seb bacon]

I say short names.  Zope isn't python, true, but they have intimate 
knowledge of each other.  If you're trying to make the validation code 
be  application-or-language-neutral, then logically you should go 
further: which other languages call mutable / immutable arrays 'tuples' 
and 'lists', or call hash tables 'dictionaries'?  Many loosely typed 
languages don't distinguish between an int and a float, and don't have 
an equivalent of tuples.  And what about long ints?

In other words, it's already strongly language-dependent.  I say, either 
go with the python way or rethink it *entirely*.  And the python way 
seems the easiest, and I'm lazy.

I'm very rarely hacking on Z3, so I'm not sure my opinion counts for 
much, but I've been enjoying following this discussion and couldn't 
resist adding something ;-)

seb


Stephan Richter wrote:
> Okay, there are two problems that need attention:
> 
> 1. Do we want long or short Field names in Schemas:
> 
> Short: Int, Float, Bool, Str, Tuple, List, Dict
> Long: Integer, Float, Boolean, String, Tuple, List, Dictionary
> 
> 2. I think the Schema package should be in lib/python/Zope and not lib/python. 
> Note that packages in Zope do NOT need to be Zope-dependent.
> 
> Please send your +1 or -1 to the list with a brief explaination about your 
> decision.
> 
> Regards,
> Stephan


-- 

    [] j a m k i t

         seb bacon
T:  020 7749 7218
F:  020 7739 8683
M:  07968 301 336
W: www.jamkit.com