[squeak-dev] translated considered harmful (in its current implementation)
marcel.taeumel at hpi.de
Wed Nov 4 08:08:51 UTC 2020
> Further, it can't be that hard, can it? Is our real problem that we don't have a specification against which we can optimize?
I gave two simple solutions for #translateInAllDomains further up in this discussion. It's doable.
Am 03.11.2020 20:34:53 schrieb Eliot Miranda <eliot.miranda at gmail.com>:
On Tue, Nov 3, 2020 at 12:29 AM Marcel Taeumel <marcel.taeumel at hpi.de [mailto:marcel.taeumel at hpi.de]> wrote:
Or just recompile #translated to do nothing in your systems. :-)
This suggestion fills me with dread. Localization seems to me to be an increasingly important facility for a development environment. And if we support it so badly that the only way to make it acceptable is to turn it off we have failed. Further, it can't be that hard, can it? Is our real problem that we don't have a specification against which we can optimize?
Am 02.11.2020 20:00:18 schrieb tim Rowledge <tim at rowledge.org [mailto:tim at rowledge.org]>:
> On 2020-11-02, at 8:17 AM, Marcel Taeumel wrote:
> Hi Tim.
> > Dare I ask why it tries to set a property on a method?
> A cache because package-name lookup for methods is expensive:
OK; I'm not brave enough to want to know why that is required. I think I'll just put a preference in for my systems and avoid the entire problem!
tim Rowledge; tim at rowledge.org [mailto:tim at rowledge.org]; http://www.rowledge.org/tim [http://www.rowledge.org/tim]
Strange OpCodes: IO: Illogical Or
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev