2008/9/10 Stéphane Ducasse <[EMAIL PROTECTED]>: >>> >> >> Well, as i said, putting FreeType into VM is simple thing. >> But maintaining a code base or regular basis is completely different >> thing. I'm not sure i have enough spare time to do this now. >> First, because i'm busy with Hydra VM. >> Second , I think you are aware, that Cog & Hydra will merge in future. >> Before this happens, i have little interest in supporting >> old-fashioned VMs :) >> >> I planning to do a major refactoring in Hydra, after which , an >> Interpreter/ObjectMemory can be simulated in image. But this will have >> a major impact on backward compatibility. >> >> But for minor changes, like in some plugins, it not hurts a lot. I >> think that, if you planning to maintain own VM, then i'll advice to >> split VMMaker package on two separate parts: >> - VM core >> - all plugins >> >> Because VM is a big code bloat , which is hard to manipulate with. >> >> Also, it would be good to have a common code repository, and separate >> tracker of bugs and fixes for VM/plugins, so it will make an >> integration easier for all interesting parties. > > could you push this idea to the VM maintainers or start to do it?
yes i could, but do you think that i have a chance to be heard and my point to be accepted? :) > We are talking abut that since years. > I still do not understand I thought that the svn of the vm code was such > common > code repository? I tried to raise this topic on board meeting, concerning status of VM-dev group and the answer was like: - we already have things set up, and each maintainer know/doing things well. I'm not sure about current status, but i keep feeling that VM maintainers efforts dissipating due to lack of communication/collaboration. Maybe it is because i'm relatively new, and missing info about how things was set up long ago, before i came in, maybe people really collaborate behind the scenes, i don't know. What i really sure about, is that , it will not hurt to call for a status (re)clarification to know who doing what and how things working. > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
