Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

> On 3 May 2018, at 10:15, Marcus Denker wrote: > > > >> On 2 May 2018, at 14:09, Marcus Denker wrote: >> >> >> >>> On 26 Apr 2018, at 09:28, Guillermo Polito >>> wrote: >>> >>> Hi, >>> >>> It looks you got bit by this issue: >>> >>> https://pharo.fogbugz.com/f/cases/21519/RemoveFrom

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

> On 2 May 2018, at 14:09, Marcus Denker wrote: > > > >> On 26 Apr 2018, at 09:28, Guillermo Polito wrote: >> >> Hi, >> >> It looks you got bit by this issue: >> >> https://pharo.fogbugz.com/f/cases/21519/RemoveFromSystem-does-not-work-well-with-Undeclareds >> >> It's not particular to E

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

> On 2 May 2018, at 17:33, Sean P. DeNigris wrote: > > Marcus Denker-4 wrote >> (I sometimes wonder if we should not late-bind accesses to globals, that >> is, just compile them as message sends to the environment). > > That would be *great*. This is another one of those little lies where > "e

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

Marcus Denker-4 wrote > (I sometimes wonder if we should not late-bind accesses to globals, that > is, just compile them as message sends to the environment). That would be *great*. This is another one of those little lies where "everything is a message send" and "late binding everything" breaks d

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

> On 2 May 2018, at 14:39, Guillermo Polito wrote: > > Well, yes to both. > > Now, about the performance, first I'd like to have a benchmark suite that > runs all the time, to at least understand if we lose some performance, > when/why was it. > Of course, this would have an impact depending

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

Well, yes to both. Now, about the performance, first I'd like to have a benchmark suite that runs all the time, to at least understand if we lose some performance, when/why was it. Of course, this would have an impact depending on how often are globals read/written. But I'd like to know with more

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

Two points. 1. Maybe we should centralize the removal of a class in a component as the class installer. So we can have it all in one place, and if we need to override and do fancy stuff. 2. Yes to the messages to the environment, I am doing so to have multiple environments sharing the same methods

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

> On 26 Apr 2018, at 09:28, Guillermo Polito wrote: > > Hi, > > It looks you got bit by this issue: > > https://pharo.fogbugz.com/f/cases/21519/RemoveFromSystem-does-not-work-well-with-Undeclareds > > It's not particular to Epicea. There should be a better management of > Undeclareds in gen

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

Yep - its that one. Needs fixing as it had me scratching my head in the wrong place … its a bit out of my league. But we are hoping to see if we can fix a few bugs at the next UK Smalltalk meeting. Tim > On 26 Apr 2018, at 08:28, Guillermo Polito > wrote: >

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

Hi, It looks you got bit by this issue: https://pharo.fogbugz.com/f/cases/21519/RemoveFromSystem-does-not-work-well-with-Undeclareds It's not particular to Epicea. There should be a better management of Undeclareds in general in all Pharo. On Thu, Apr 26, 2018 at 8:44 AM, Tim Mackinnon wrote:

Re: [Pharo-users] Restoring a class via Epicea didn't recompile a reference?

That should be “re-saved “ it, the issue went away. Sent from my iPhone > On 25 Apr 2018, at 23:43, Tim Mackinnon wrote: > > Hi - I think I had this issue a long while back, but I just hit it again > (desperately trying to get back into Pharo again)… > > I was trying out Willow - and had a m

[Pharo-users] Restoring a class via Epicea didn't recompile a reference?

Hi - I think I had this issue a long while back, but I just hit it again (desperately trying to get back into Pharo again)… I was trying out Willow - and had a method like this: initializeContainerView | behaviorDetails scopeSelection | behaviorDetails := IdentifiedWebView