[Pharo-project] VM Plugins internal vs external
Hi, What is the difference between internal and external plugins in the VM? Noury
From what i know, it has more to do with having smaller sized vm's, than with efficiency reasons.
On Sep 20, 2010, at 9:38 AM, Noury Bouraqadi wrote:
Hi,
What is the difference between internal and external plugins in the VM?
Noury
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Noury! Well the internal plugins are part of the vm executable and the external plugins are shipped as separate shared library files. The interface to both variants is the same, but not every vm plugin might work as an external or internal plugin depending on the implementation. I don't know if this is still true, but there was also the idea, that an external plugin "overrides" an internal version. So in the case of a malfunctioning internal plugin, you could ship a new external plugin of the same name that will be used instead of the internal one when placed in a location of the vm plugin paths. But that's all out of my flaky memory and could be totally different nowadays.:) Alex 2010/9/20 Noury Bouraqadi <bouraqadi@gmail.com>:
Hi,
What is the difference between internal and external plugins in the VM?
Noury
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Also, some of the plugins are meant to be internal for forever, since they are tightly bound with VM and its basic functionalities (files, bitblt etc). Some other plugins are meant to be only external, and they even not build if you try to build them as internal ones. On 20 September 2010 13:07, Alexander LazareviÄ <laza@blobworks.com> wrote:
Hi Noury!
Well the internal plugins are part of the vm executable and the external plugins are shipped as separate shared library files. The interface to both variants is the same, but not every vm plugin might work as an external or internal plugin depending on the implementation. I don't know if this is still true, but there was also the idea, that an external plugin "overrides" an internal version. So in the case of a malfunctioning internal plugin, you could ship a new external plugin of the same name that will be used instead of the internal one when placed in a location of the vm plugin paths. But that's all out of my flaky memory and could be totally different nowadays.:)
Alex
2010/9/20 Noury Bouraqadi <bouraqadi@gmail.com>:
Hi,
What is the difference between internal and external plugins in the VM?
Noury
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
participants (4)
-
Alexander LazareviÄ -
Fernando olivero -
Igor Stasenko -
Noury Bouraqadi