Hi All,
I had a discussion about plugin version numbers on reddit. http://programming.reddit.com/info/2s4eh/comments/c2t32y?context=5 .
What do people think about adding version numbers to plugins like LargeIntegersPlugin class>>moduleNameAndVersion.
Is this something we should be encouraging or do people really not see the benefit?
Thanks,
Ron Teitelbaum
On Mon, Sep 24, 2007 at 05:16:17PM -0400, Ron Teitelbaum wrote:
What do people think about adding version numbers to plugins like LargeIntegersPlugin class>>moduleNameAndVersion.
Is this something we should be encouraging or do people really not see the benefit?
For the plugins that I maintain, I use #primitiveVersionString and #primitiveModuleName to enable the loaded plugin to identify itself. On the class side, I use #versionString to identify the version at compile time, along with the existing class method #moduleName to identify the module. I've been using this convention for quite a while, and it works well for tracking the version of the plugin source as well as providing a mechanism to test the version level of whatever module got loaded at runtime.
The implementation of #moduleNameAndVersion in LargeIntegersPlugin looks quite reasonable, and I'd be happy to support that as a convention also.
Dave
I'd say that adding a prim to plugins for this would be fine as long as it returns the same info as provided for Smalltalk listLoadedPlugins etc. I'd hate to see info-skew confusing people.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Original Sin is hard to find, but the digitally enhanced version is readily available.
vm-dev@lists.squeakfoundation.org
-
David T. Lewis -
Ron Teitelbaum -
tim Rowledge