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 |
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 <[hidden email]> wrote: AbstractLauncher was removed in: http://code.google.com/p/pharo/issues/detail?id=4002 -- Mariano http://marianopeck.wordpress.com |
sooo.. opinions? On Sun, Apr 24, 2011 at 8:11 PM, Mariano Martinez Peck <[hidden email]> 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. -- Mariano http://marianopeck.wordpress.com |
On Tue, May 10, 2011 at 12:26 PM, Mariano Martinez Peck <[hidden email]> wrote:
Split Cog into sub-packages, pulling out the command line evaluator, which is a test case for the threaded FFI, into a sub-package of its own.
|
On 10 May 2011 23:32, Eliot Miranda <[hidden email]> wrote: > > > > On Tue, May 10, 2011 at 12:26 PM, Mariano Martinez Peck <[hidden email]> wrote: >> >> >> sooo.. opinions? > > Split Cog into sub-packages, pulling out the command line evaluator, which is a test case for the threaded FFI, into a sub-package of its own. Any suggestions what name of package should be , and where is better to place it in FFI project repository or VMMaker project repository? >> On Sun, Apr 24, 2011 at 8:11 PM, Mariano Martinez Peck <[hidden email]> 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 <[hidden email]> 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 >> >> > > > -- Best regards, Igor Stasenko AKA sig. |
Free forum by Nabble | Edit this page |