<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bert Freudenberg wrote:
<blockquote
cite="mid:FC643CF3-A4B4-48AC-BBC3-1089DDB68AD8@freudenbergs.de"
type="cite">
<pre wrap=""> </pre>
<br>
<hr size="4" width="90%"><br>
<meta http-equiv="Content-Type" content="text/html ">
<br>
<div>
<div>On 17.07.2014, at 22:52, gettimothy <<a moz-do-not-send="true"
href="mailto:gettimothy@zoho.com">gettimothy@zoho.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<div>
<div
style="font-size: 10pt; font-family: Verdana,Arial,Helvetica,sans-serif;">
<div>Hi Eliot.<br>
</div>
<div><br>
</div>
<div>thx for the reply.</div>
<div><br>
</div>
<div>The goal I am pursing is a consistent mapping of terms from
the metal to the smalltalk level. If something is 'turtles' then I want
it to be 'turtles' all the way down the chain.</div>
<div><br>
</div>
<div><br>
<blockquote
style="border: 1px solid rgb(204, 204, 204); padding: 7px; background-color: rgb(245, 245, 245); position: static; z-index: auto;">Looking
at platforms/unix/vm/SqModule.h, which declares the metaprotocol of
these things, arg parsing, help, launch, etc, it's clear these things
are VM modules, which is different from plugins. But you might ask Ian
Piumarta directly.</blockquote>
<br>
Ian handles them in his CMake script with the term plugins_vm per this
code in trunk/platforms/unix/cmake/Plugins.cmake</div>
<div><br>
</div>
<br>
<blockquote
style="border: 1px solid rgb(204, 204, 204); padding: 7px; background-color: rgb(245, 245, 245);">
<div id="1">MACRO (CONFIGURE_PLUGINS)<br>
CONFIGURE_PLUGIN_LIST (plugins_int)<br>
CONFIGURE_PLUGIN_LIST (plugins_ext)<br>
CONFIGURE_PLUGIN_LIST (plugins_vm)<br>
ENDMACRO (CONFIGURE_PLUGINS)</div>
</blockquote>
<div><br>
</div>
<div>I prefer the term VMModules as that reflects the heuristics
you use; I am ok with pluginsVM too as that mimics Ian's code. I will
be replacing the term vmDrivers tomorrow when I can pry my eyes back
open.<br>
</div>
</div>
</div>
</blockquote>
</div>
<div><br>
</div>
<div>Formally we call the VM extensions "modules" (e.g.
listLoadedModules). Informally they are known as VM plugins. And that
informal use has spread, so by now we use the terms interchangeably. <br>
</div>
</blockquote>
<br>
To my mind, a module is something that might only be able to be bound
at VM compile time, whereas a plugin could be bound to a running VM. I
guess that at some point of history there was only the former, and the
latter came along later with new terminology?<br>
cheers -ben<br>
<br>
<blockquote
cite="mid:FC643CF3-A4B4-48AC-BBC3-1089DDB68AD8@freudenbergs.de"
type="cite">
<div><br>
</div>
<div>Internal and external modules are supported by pretty much all
VMs, providing named primitives and getting loaded on-demand when a
named primitive is invoked.</div>
<div><br>
</div>
<div>Ian's drivers are unique and use the module mechanism mostly to
avoid code duplication. But they are different, they do not provide
named primitives, they get loaded on VM startup. They provide
alternative implementations of the same platform functions, which is
necessary because Unix is a much more diverse platform than the others. </div>
<br>
<div><span class="Apple-style-span"
style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;">
<div style="">
<div style="font-family: Helvetica;"><span class="Apple-style-span"
style="font-family: Helvetica;">- Bert -</span></div>
<br class="Apple-interchange-newline">
</div>
</span><br class="Apple-interchange-newline">
</div>
<br>
</blockquote>
<br>
</body>
</html>