Le 15/2/16 14:10, Mariano Martinez Peck a écrit :
On Mon, Feb 15, 2016 at 7:15 AM, Denis Kudriashov
<[email protected] <mailto:[email protected]>> wrote:
Hello.
I think it is important to get single proxy framework for Pharo.
It should provide required integration support for our tools.
I want push Ghost in that direction. Debuggers and inspectors
should work correctly with proxies which based on Ghost.
Hi Denis,
I welcome you push on Ghost. The original source of Ghost was in SS3
and then, the CAR team move it to Shub and hence why it is there. I
THINK they did not do many changes from the "upstream" project, so it
should be safe to take that one. I guess you should ask Luc Fabrese
about that.
Debugging, inspecting, etc was some of the problems that Ghost did
solve. I was able to do all that. And you were able to enable/disabled
debugging capabilities dynamically.
What I really really really recommend you is that before doing
anything with Ghost, please read the whole journal paper as there is a
lot of discussion, possibilities, explanations of why we took path X,
etc etc:
https://hal.inria.fr/hal-01081236/file/Mart14z-Ghost-Final.pdf
Now Ghost is stored in CAR team repository. Should we move it to
Pharo?
I know that is is subjective, but from my latest experience with git,
if I were to make the move of a repository (which requires some
effort) I would do it to github.
No core package of Pharo should be managed with git.
We will move all together and not pieces by pieces.
Finally, let me say something.... what I got from my Ghost proxies
experience is that Ghost could serve as a proxy library for "common"
usage. The code of Ghost is very very little. What is most important
is the idea, not the code. This is why, many of the people that got
interested in using Ghost for a project X, they ended up "forking" the
original Ghost code and adapt it. So...while Ghost can be used and
extended for different purposes, I think it's not bad either that
someone forks it and adjusts it for his needs.
P.S. Ghost has one failed tests due to Spur problem 17536
<https://pharo.fogbugz.com/f/cases/17536/VM-Crash-when-adding-an-iVar-to-a-subclass-of-SystemAnnouncement>.
Best regards,
Denis
--
Mariano
http://marianopeck.wordpress.com
