On 14/12/09 21:32 +0100, Hartmut Goebel wrote:
> Cédric Krier schrieb:
> > On 14/12/09 19:32 +0100, Hartmut Goebel wrote:
>
> >>>> [{'__class__': 'eval', 'v': "['parent', '=', False]"}]
> >>>> {'company': {'__class__': 'eval', 'v': "company or False"}}
> >>>> {'__class__': 'eval', 'v': "[16, currency_digits]"}
> >>>> {'__class__': 'eval', 'v': "len(lines) and True or False"}
> >> This is terrible unreadable! We should not expose this to the user nor
> >> to the programmer. It looks ugly and is redundant.
> >
> > There is no redundant.
>
> From my point of view, there is a lot of redundancy:
> {'__class__': 'eval', 'v':
> is in every line.
>
> >> Maybe we could extend your idea towards some function-oriented style.
> >> This should allow a very simple implementation on almost every language
> >> suporting some kind of 'evel()'. In Python this could be implemented
> >> quite easily like in the example: http://dpaste.org/kIZy/
> >
> > I don't understand as you say you don't want to change the language.
>
> I do not want to change the language, the user/programmer uses. But I
> understood that we need to change the parameters passed to the clients,
> since this needs to be language-independent.It is a change because for now we use full python syntax. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email: [email protected] Jabber: [email protected] Website: http://www.b2ck.com/ twitter: http://twitter.com/cedrickrier identi.ca: http://identi.ca/cedrickrier
pgpBJy162uo29.pgp
Description: PGP signature
