On May 12, 2011, at 3:42 PM, Mariano Martinez Peck wrote:

sooo.. opinions?

We can add the class the the compatiblity package...

On Sun, Apr 24, 2011 at 8:11 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote: If Cog really needs it we should create a separate repostiroy like PharoCogSupport and put the class there and add it as a dependency of Cog in ConfigurationOfCog. Another hacky way is to add a #preLoadDoit: in ConfigurationOfCog that does a #compile: of AbstractLauncher

Cheers

Mariano

On Sun, Apr 24, 2011 at 7:37 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote: AbstractLauncher was removed in: http://code.google.com/p/pharo/issues/detail?id=4002

Cog has a subclass from AbstractLauncher called CommandLineLauncher, hence, it cannot be loaded anymore

CommandLineLauncher has no class comment and no sender. So I have no idea what it does, nor if it can be removed from cog, nor how to solve this problem in Pharo.

Cheers

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

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

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

-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.