Moving VMMakerTool to a separate package

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Moving VMMakerTool to a separate package

Mariano Martinez Peck
 
Hi guys. What do you think about moving VMMakerTool to a separate package ?  Not only because Cog (at least in the Workspaces and instructions from Eliot) and CMakeVMMaker do not use it any more, but also because it is rather common to separate the "model" from the "view". 

Cheers

--
Mariano
http://marianopeck.wordpress.com

Reply | Threaded
Open this post in threaded view
|

Re: Moving VMMakerTool to a separate package

David T. Lewis
 
On Mon, Apr 18, 2011 at 07:16:03PM +0200, Mariano Martinez Peck wrote:
>  
> Hi guys. What do you think about moving VMMakerTool to a separate package ?
> Not only because Cog (at least in the Workspaces and instructions from
> Eliot) and CMakeVMMaker do not use it any more, but also because it is
> rather common to separate the "model" from the "view".

Ideally the current VMMaker package should be separated into a number
of packages (code generators separate from interpreters, etc). But I
think that taking on repackaging right now would be confusing. First
priority is code making progress on code merges, repackaging the result
can wait for calmer days.

BTW, for a reasonable packaging structure just look at any old
Squeak image from the pre-VMMaker days.

Dave