Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Camillo Bruni
Have a look at ClassBoxes: http://scg.unibe.ch/archive/papers/Berg03aClassboxes.pdf I think they come pretty close to what you have in mind. On 2013-02-03, at 12:30, Denis Kudriashov wrote: > Hello. > > Some days ago I think about how java works with dependencies and how it can > be implement

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Frank Shearar
On 3 February 2013 11:36, Camillo Bruni wrote: > Have a look at ClassBoxes: > > http://scg.unibe.ch/archive/papers/Berg03aClassboxes.pdf > > I think they come pretty close to what you have in mind. > > On 2013-02-03, at 12:30, Denis Kudriashov wrote: > >> Hello. >> >> Some days ago I think about

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Denis Kudriashov
2013/2/3 Frank Shearar > >> For java example libA.jar uses SharedClass.methodA and libB.jar uses > >> SharedClass.methodB. But #methodA exists only in version deployed as > >> libS-a.jar. And #methodB exists only in version deployed as libS-b.jar. > >> Dependency from libA.jar on libS-a.jar and l

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Frank Shearar
On 3 February 2013 15:42, Denis Kudriashov wrote: > 2013/2/3 Frank Shearar >> >> >> For java example libA.jar uses SharedClass.methodA and libB.jar uses >> >> SharedClass.methodB. But #methodA exists only in version deployed as >> >> libS-a.jar. And #methodB exists only in version deployed as lib

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Miguel Moquillon
And the Java people are preparing to throw away the classloaders mechanism with Jigsaw that will be in Java 9. (The classloading is a brittle and error-prone mechanism.) The aim of jigswa is to design and implement a new module system for the Java SE platform and to apply that sys­tem to the pla

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Denis Kudriashov
2013/2/3 Frank Shearar > On 3 February 2013 15:42, Denis Kudriashov wrote: > > 2013/2/3 Frank Shearar > >> > >> >> For java example libA.jar uses SharedClass.methodA and libB.jar uses > >> >> SharedClass.methodB. But #methodA exists only in version deployed as > >> >> libS-a.jar. And #methodB e

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Denis Kudriashov
2013/2/3 Miguel Moquillon > And the Java people are preparing to throw away the classloaders mechanism > with Jigsaw that will be in Java 9. (The classloading is a brittle and > error-prone mechanism.) > The aim of jigswa is to design and implement a new module system for the > Java SE platform a

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Denis Kudriashov
2013/2/3 Camillo Bruni > Have a look at ClassBoxes: > > http://scg.unibe.ch/archive/papers/Berg03aClassboxes.pdf > > I think they come pretty close to what you have in mind. > Thank's for link. I think classboxies can be good basis to implement my requirement. Separated classbox per package vers

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Miguel Moquillon
Le 03/02/2013 19:27, Denis Kudriashov a écrit : 2013/2/3 Miguel Moquillon > > > > And the Java people are preparing to throw away the classloaders > mechanism with Jigsaw that will be in Java 9. (The classloading is a > brittle and error-prone mechanism.) The

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Frank Shearar
On 3 February 2013 19:53, Miguel Moquillon wrote: > Le 03/02/2013 19:27, Denis Kudriashov a écrit : >> 2013/2/3 Miguel Moquillon > > > >> >> And the Java people are preparing to throw away the classloaders >> mechanism with Jigsaw that will be in Java 9. (The cla

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Igor Stasenko
On 3 February 2013 20:53, Miguel Moquillon wrote: > Le 03/02/2013 19:27, Denis Kudriashov a écrit : >> 2013/2/3 Miguel Moquillon > > > >> >> And the Java people are preparing to throw away the classloaders >> mechanism with Jigsaw that will be in Java 9. (The cla

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Frank Shearar
On 3 February 2013 20:42, Igor Stasenko wrote: > On 3 February 2013 20:53, Miguel Moquillon wrote: >> Le 03/02/2013 19:27, Denis Kudriashov a écrit : >>> 2013/2/3 Miguel Moquillon >> > >> >>> >>> And the Java people are preparing to throw away the classloaders >

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Lawson English
dare I mention Craig Latta's Spoon project which explicitly is meant to solve this issue? L On 2/3/13 1:42 PM, Igor Stasenko wrote: On 3 February 2013 20:53, Miguel Moquillon wrote: Le 03/02/2013 19:27, Denis Kudriashov a écrit : 2013/2/3 Miguel Moquillon mailto:miguel.moquil...@gmail.com>>

Re: [Pharo-project] Future "Modules system"

2013-02-03 Thread Igor Stasenko
On 4 February 2013 01:23, Lawson English wrote: > dare I mention Craig Latta's Spoon project which explicitly is meant to > solve this issue? > in what way? being able to exchange data between two images ~~ being able to deal with two different versions of same class properly. Think about proper s

Re: [Pharo-project] Future "Modules system"

2013-02-04 Thread Lawson English
Well, the tools available are still relatively primitive, but bugs aside, the current version of Spoon has the capability of creating and editing methods in a "remote" spoon image using a class browser living in the main image which looks and behaves exactly like a normal Pharo/Squeak image exc

Re: [Pharo-project] Future "Modules system"

2013-02-04 Thread Martin Dias
I arrived to almost the same problem some weeks ago, when I was thinking on how to have multiple versions of Fuel at the same time, so one can, for example, easily migrate her files to a newer version. Fuel has lots of extension methods, so we need also multiple versions of the same extension meth

Re: [Pharo-project] Future "Modules system"

2013-02-04 Thread Martin Dias
On Mon, Feb 4, 2013 at 4:15 PM, Martin Dias wrote: > Then, I arrived to ClassBoxes paper, from which I would like to Hmmm, I misread. Actually the paper I was talking about is the ChangeBoxes one. So I wanted to play with that but without tracking the changes as they do...

Re: [Pharo-project] Future "Modules system"

2013-02-04 Thread Denis Kudriashov
Hi 2013/2/4 Martin Dias > I arrived to almost the same problem some weeks ago, when I was > thinking on how to have multiple versions of Fuel at the same time, so > one can, for example, easily migrate her files to a newer version. > > Fuel has lots of extension methods, so we need also multiple

Re: [Pharo-project] Future "Modules system"

2013-02-04 Thread Martin Dias
On Mon, Feb 4, 2013 at 5:25 PM, Denis Kudriashov wrote: > Hi > > 2013/2/4 Martin Dias >> >> I arrived to almost the same problem some weeks ago, when I was >> thinking on how to have multiple versions of Fuel at the same time, so >> one can, for example, easily migrate her files to a newer versio

Re: [Pharo-project] Future "Modules system"

2013-02-04 Thread Craig Latta
Hi-- Yes, Spoon[1] supports multiple active versions of the same class. Background: Spoon has no system dictionary, nor does it use "chunk-format" files such as sources or changes files, or "fileouts". It doesn't use files at all, apart from object memory snapshots and virtual ma

Re: [Pharo-project] Future "Modules system"

2013-02-07 Thread Craig Latta
Oh, and I'm testing Naiad support for all the Smalltalk systems I know: Pharo, Squeak, VisualWorks, VAST, ObjectStudio, GNU Smalltalk, Amber, Redline Smalltalk, and Dolphin Smalltalk. Please let me know of any still in existence that I overlooked. I think there are possibilities for Self and