Hi Paolo,
I can mentor the project below:
> Project idea
>
> Name: Instance Derreferencer for Pharo
> Skill level: Intermediate
> Possible Mentors:
> Name of the Student: Alejandro Infante
>
> Description:
> A problem with image based environment is, when you detect a memory leak is
> removing
On Fri, 14 Feb 2014, Alexandre Bergel wrote:
Hi Paolo,
I can mentor the project below:
Project idea
Name: Instance Derreferencer for Pharo
Skill level: Intermediate
Possible Mentors:
Name of the Student: Alejandro Infante
Description:
A problem with image based environment is, when you detec
Well... I do no think so. There is a fair amount of work regarding memory
profiling. Dereferencing is probably only a small piece off.
Anyway, we will have time to refine the project description
Alexandre
> Le 14-02-2014 à 18:17, Levente Uzonyi a écrit :
>
>> On Fri, 14 Feb 2014, Alexandre Be
FYI writing any decent production quality tool takes way more than 1
hour. IME writing *two* reference finders, it takes a bunch of effort
to make them work correctly, reliably, quickly, and in a useful way.
On 2/15/14 6:31 , Alexandre Bergel wrote:
Well... I do no think so. There is a fair a
On Sat, 15 Feb 2014, Andres Valloud wrote:
FYI writing any decent production quality tool takes way more than 1 hour.
IME writing *two* reference finders, it takes a bunch of effort to make them
work correctly, reliably, quickly, and in a useful way.
I would agree with you if the building blo
Well, I tried today using that to release some memory used by Roassal.
Let's say all the instances of ROElement. So I executed the following code:
ROElement allInstances do: [:el | el becomeForward: nil ].
The next second the image crashed. Then I thought that was because the
visualization was op
All that I said was "it takes way more than 1 hour".
The "useful" part comes in when e.g. "inboundPointers" reveals stuff
that should also be gone. So now you need a full blown reference
finder, and getting one of those to work quickly and correctly is not
trivial. Also with some objects you
On Sat, 15 Feb 2014, Alejandro Infante wrote:
Well, I tried today using that to release some memory used by Roassal. Let's
say all the instances of ROElement. So I executed the following code:
ROElement allInstances do: [:el | el becomeForward: nil ].
The next second the image crashed. Then I
On 2/16/14 3:38 , Levente Uzonyi wrote:
On Sat, 15 Feb 2014, Alejandro Infante wrote:
Well, I tried today using that to release some memory used by
Roassal. Let's say all the instances of ROElement. So I executed
the following code:
ROElement allInstances do: [:el | el becomeForward: nil ].
T
On Sat, 15 Feb 2014, Andres Valloud wrote:
All that I said was "it takes way more than 1 hour".
The "useful" part comes in when e.g. "inboundPointers" reveals stuff that
should also be gone. So now you need a full blown reference finder, and
getting one of those to work quickly and correctly
10 matches
Mail list logo
