[etoys-dev] Translation support

Hilaire Fernandes hilaire.fernandes at edu.ge.ch
Tue May 4 13:26:10 EDT 2010

Bert Freudenberg a écrit :

> I'm just talking about an implementation detail. You do not have to 
> worry about it, just use #translated in your code as usual.

But I am interested by the implementation detail. I also want it ported 
to pharo.

> "Method properties" are additional state you can attach to a compiled 
> method. Similar to pragmas, but invisible. They are not created by tags 
> in the source code while compiling, but are attached later. 

Ok, thanks to explain.

> I'm just proposing to use them to cache the translation domain for a 
> method.

Ok, what is exactly translation domain, is it text domain?

> Figuring this out properly at runtime is expensive (the code 
> needs to work its way from the compiled method to the package it belongs 
> to).

Is it really expensive ? I can't evaluate.

> With this I think we could even get rid of the class registration? The 
> translation domain would just be the package name of the method that 
> sent #translated. How does that sound?   

More information about the etoys-dev mailing list