Hi Arturo
May be you spot a bug, sadly. I remember that we got a problem in the
past and I thought it was fixed.
You can use Epicea the new and working change recording system developed
by Martin Dias.
Stef
On 18/5/14 14:58, Arturo Zambrano wrote:
Hi All,
Trying to recover lost changes f
2014-05-18 21:42 GMT+02:00 Johan Fabry :
>
> I understand, thanks for the info.
>
> Let me simplify my question: Using slots is there a reasonably
> straightforward way for me to intercept variable accesses in all methods
> within a class?
Yes. This is easy to do with slots.
Basically you need
http://www.lighttable.com/2014/05/16/pain-we-forgot/
Newspeak is indirectly referenced, but no mention of Smalltalk until near the
end of the article. Smalltalk does crop up in the comments.
http://www.reddit.com/r/programming/comments/25tias/pain_we_forgot/
/Garth
I understand, thanks for the info.
Let me simplify my question: Using slots is there a reasonably straightforward
way for me to intercept variable accesses in all methods within a class? This
so that I can transparently redirect them to a dictionary lookup. Or am I going
to have to override i
Hi All,
Trying to recover lost changes from another (broken) image I noticed
that only method definition and do-it are saved.
I'm in a middle of a refactoring where I changed hierarchies, renamed
classes and inst vars.
When trying to recover the changes, class name changes are not there, so
It is really a nice way to announce/talk smartly and originally on Pharo
release out there.
Thanks
Hilaire
Le 18/05/2014 09:52, Tudor Girba a écrit :
> Hi,
>
> I was asked several times for how the visualization from the Pharo 3.0
> announcement was created. I now put together a blog post to ex
Hi,
I was asked several times for how the visualization from the Pharo 3.0
announcement was created. I now put together a blog post to explain it:
http://www.humane-assessment.com/blog/communicating-changes-in-pharo-3-0
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hello,
Actually slots are introduced so we can use them the next Pharo iteration
(Pharo 4). It is difficult to use as it is, you need to change a bit the
compiler so that it asks the class slots for field access byte code
generation (a field being typically an instance variable) and you also need
