June 2010 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Alien for Squeak 4.1/Pharo 1.1?

by StÃ©phane Ducasse

On Jun 9, 2010, at 9:32 AM, Joachim Geidel wrote: > > Am 09.06.10 08:06 schrieb StÃ©phane Ducasse: >> We would love to have a version of alien working for pharo on all platform. > > IMO, this would make it necessary to move all extensions of system classes > (with the exception of the #asAlien conversion methods) to Alien-Prereqs, > and have different versions of this package for Pharo 1.0, Pharo 1.1, and > Squeak 4.1. Can this be done with Metacello, or is Metacello a Pharo-only > thing? I am a newbie here, I simply haven't had the time to look at > Metacello yet. > > Also, the override of > SystemDictionary/SmalltalkImage>>recreateSpecialObjectsArray has to be > eliminated. I have seen that the current Squeak and Pharo images have a 50 > element specialObjectsArray, Alien adds 5 more entries, and there is another > version in the pipeline for Squeak which adds one more for finalization > support. after discussing with igor this point we decided to wait to see what was happening since it made no sense to change this method all the time but to wait for a new VM. > That leaves us with three different versions already. IMHO, it is > not acceptable to override that method. What's needed is a possibility to > extend the array using a well-defined API, intended for VM developers only, > of course. There is a better solution as discussed in the vm mailing-list. Igor proposed a solution and now we are waiting. > >>> In Squeak, this meant removing the Alien-Prereqs package and all >>> Parser/Scanner/MethodNode changes, >> >> what are these? > > Ups, sorry for the confusion. There are changes of Parser and Scanner in > Alien-Prereqs, while Alien-Core contains methods for MethodNode, Compiler, > Decompiler, and CompiledMethod. Most of the latter only change the > printStrings of MethodNodes and CompiledMethods for primitives, and all of > them seem to be completely unnecessary in Squeak 4.1. One method in > MethodNode (MethodNode>>generate) overrides a different implementation both > in Squeak 4.1 and Pharo 1.1, and does not work in both of them. Most of the > overridden methods in Alien-Prereqs actually only changed the error messages > emitted when parsing method sources, others seem to be precursors of methods > which have been integrated into Squeak about two years ago. cleaning the package would be a nice first step. > >>> as they are redundant or obsolete in >>> Squeak 4.1. I have a version of the Alien-Core Monticello package which >>> loads cleanly in Squeak 4.1, if anybody is interested. However, this package >>> does not load in Pharo 1.1 beta 11367 - some of the changes I removed still >>> seem to be needed there. >> >> can you point us to them? > > Not yet. I didn't want to waste my time with an analysis before knowing if > someone else is working on this issue, and might already know what has to be > done. > > Joachim Geidel > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 9, 2010

Re: [Pharo-users] Alien for Squeak 4.1/Pharo 1.1?

by Joachim Geidel

Am 09.06.10 08:06 schrieb StÃ©phane Ducasse: > We would love to have a version of alien working for pharo on all platform. IMO, this would make it necessary to move all extensions of system classes (with the exception of the #asAlien conversion methods) to Alien-Prereqs, and have different versions of this package for Pharo 1.0, Pharo 1.1, and Squeak 4.1. Can this be done with Metacello, or is Metacello a Pharo-only thing? I am a newbie here, I simply haven't had the time to look at Metacello yet. Also, the override of SystemDictionary/SmalltalkImage>>recreateSpecialObjectsArray has to be eliminated. I have seen that the current Squeak and Pharo images have a 50 element specialObjectsArray, Alien adds 5 more entries, and there is another version in the pipeline for Squeak which adds one more for finalization support. That leaves us with three different versions already. IMHO, it is not acceptable to override that method. What's needed is a possibility to extend the array using a well-defined API, intended for VM developers only, of course. >> In Squeak, this meant removing the Alien-Prereqs package and all >> Parser/Scanner/MethodNode changes, > > what are these? Ups, sorry for the confusion. There are changes of Parser and Scanner in Alien-Prereqs, while Alien-Core contains methods for MethodNode, Compiler, Decompiler, and CompiledMethod. Most of the latter only change the printStrings of MethodNodes and CompiledMethods for primitives, and all of them seem to be completely unnecessary in Squeak 4.1. One method in MethodNode (MethodNode>>generate) overrides a different implementation both in Squeak 4.1 and Pharo 1.1, and does not work in both of them. Most of the overridden methods in Alien-Prereqs actually only changed the error messages emitted when parsing method sources, others seem to be precursors of methods which have been integrated into Squeak about two years ago. >> as they are redundant or obsolete in >> Squeak 4.1. I have a version of the Alien-Core Monticello package which >> loads cleanly in Squeak 4.1, if anybody is interested. However, this package >> does not load in Pharo 1.1 beta 11367 - some of the changes I removed still >> seem to be needed there. > > can you point us to them? Not yet. I didn't want to waste my time with an analysis before knowing if someone else is working on this issue, and might already know what has to be done. Joachim Geidel

June 9, 2010

Re: [Pharo-users] JNIPort preview for Pharo available on SqueakSource

by StÃ©phane Ducasse

On Jun 9, 2010, at 7:35 AM, Tudor Girba wrote: > Hi Johan, > > It is not only reasoning about Java. A connection to Java is very useful to communicate with Java libraries (for example, graph libraries). +1 such as a PHP parser > Also, what Johan Brichau did in VW was to directly query Eclipse for reasoning about Java. Pretty cool :) > > Cheers, > Doru > >

June 9, 2010

Re: [Pharo-users] Alien for Squeak 4.1/Pharo 1.1?

by StÃ©phane Ducasse

We would love to have a version of alien working for pharo on all platform. On Jun 8, 2010, at 9:49 PM, Joachim Geidel wrote: > I somehow managed to load Alien into both Squeak 4.1 and Pharo 1.1. You can > see what I had to do in the installation instructions for JNIPort on > SqueakSource. It's not for the faint of heart... ;-) > > In Squeak, this meant removing the Alien-Prereqs package and all > Parser/Scanner/MethodNode changes, what are these? > as they are redundant or obsolete in > Squeak 4.1. I have a version of the Alien-Core Monticello package which > loads cleanly in Squeak 4.1, if anybody is interested. However, this package > does not load in Pharo 1.1 beta 11367 - some of the changes I removed still > seem to be needed there. can you point us to them? > > What are the plans for Alien? When will it be made available for Squeak 4.1 > and Pharo 1.1? I am interested in this because I need Alien as the base for > JNIPort, and I would like to at least run the JNIPort test suite on a stable > version of Alien before officially releasing JNIPort 2.0. > > Joachim Geidel > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 9, 2010

Re: [Pharo-users] JNIPort preview for Pharo available on SqueakSource

by Tudor Girba

Hi Johan, It is not only reasoning about Java. A connection to Java is very useful to communicate with Java libraries (for example, graph libraries). Also, what Johan Brichau did in VW was to directly query Eclipse for reasoning about Java. Pretty cool :) Cheers, Doru On 8 Jun 2010, at 23:27, Johan Fabry wrote: > > The problem with the Moose and reasoning about Java thing (I think > this is what you are thinking about) is to keep the importer > maintained, as Doru convinced me. In the end the infusion way works > OK for me, so right now I am not looking for another solution. If > one presents itself I am happy to give it a try :-) > > On 08 Jun 2010, at 11:13, StÃ©phane Ducasse wrote: > >> Cool we are really busy but really interested. >> We want to connect moose to java.... so what you are doing and also >> johan is key for us. >> >> On Jun 7, 2010, at 7:07 PM, Joachim Geidel wrote: >> >>> I have made a preview release of JNIPort for Pharo/Squeak >>> available on SqueakSource: >>> http://www.squeaksource.com/JNIPort.html >>> >>> JNIPort is a Smalltalk library which allows Java code to be >>> invoked from Smalltalk. It acts as a bridge between the world of >>> Smalltalk objects and a Java Virtual Machine (JVM) where Java code >>> is executing. >>> >>> If you want to know what can be done with JNIPort, see >>> http://philemonworks.wordpress.com/2010/04/29/google-api-access-from-smallt… >>> for an example. >>> >>> Installation instructions are on the Wiki at SqueakSource. See http://jniport.wikispaces.com/ >>> for more information about JNIPort. >>> >>> The current state of the Pharo/Squeak version of JNIPort (as of 7 >>> June 2010): >>> â¢ Callbacks from Java to Smalltalk are not yet supported. >>> â¢ In contrast to VisualWorks and Dolphin, JNIPort does not create >>> ghost classes as wrappers for Java classes, but creates ârealâ >>> classes which can be seen in the system browser. It also does not >>> copy prototypes of CompiledMethods when a wrapper class or a Java >>> class is created, because this causes VM failures in Pharo 1.0. >>> Instead, methods are compiled from source code. This has a >>> performance impact, of course. >>> â¢ Another difference from the VisualWorks and Dolphin versions is >>> that wrappers for Java methods without arguments donât have >>> selectors ending with an awkward â_nullâ suffix. >>> â¢ JNIPort has been developed and tested with Pharo 1.0 on Mac OS >>> X 10.6.3. If it works in Squeak and on other operating systems has >>> yet to be tested. >>> â¢ I have briefly tested JNIPort with Pharo 1.1 beta 11367, but >>> this needed some manual modifications of Alien â without them >>> Alien causes problems in Pharo 1.1. >>> â¢ In Pharo 1.1, starting a JVM needs 11 seconds vs. 4 seconds in >>> Pharo 1.0. I donât know yet why. >>> â¢ I donât have a Metacello configuration yet. >>> >>> The next steps will be: >>> â¢ Adding support for callbacks from Java to Smalltalk. >>> â¢ Testing it on more platforms. >>> â¢ Reorganization of the documentation on the JNIPort wiki, and >>> addition of Pharo/Squeak specific documentation similar to the >>> documentation for the VisualWorks version. >>> â¢ Release of JNIPort 2.0 for VisualWorks and Pharo/Squeak when >>> everything is stable. This will be after the release of Pharo 1.1. >>> >>> If it works in Squeak 4.1 or on Linux or Windows, please let me >>> know, especially if you had to do something which might be worth >>> mentioning in the installation instructions. >>> >>> Have fun with JNIPort, and let me know if it works! >>> >>> Joachim Geidel >>> _______________________________________________ >>> Pharo-users mailing list >>> Pharo-users(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > -- > Johan Fabry > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- www.tudorgirba.com "Reasonable is what we are accustomed with."

June 9, 2010

Re: [Pharo-users] JNIPort preview for Pharo available on SqueakSource

by Johan Fabry

The problem with the Moose and reasoning about Java thing (I think this is what you are thinking about) is to keep the importer maintained, as Doru convinced me. In the end the infusion way works OK for me, so right now I am not looking for another solution. If one presents itself I am happy to give it a try :-) On 08 Jun 2010, at 11:13, StÃ©phane Ducasse wrote: > Cool we are really busy but really interested. > We want to connect moose to java.... so what you are doing and also johan is key for us. > > On Jun 7, 2010, at 7:07 PM, Joachim Geidel wrote: > >> I have made a preview release of JNIPort for Pharo/Squeak available on SqueakSource: >> http://www.squeaksource.com/JNIPort.html >> >> JNIPort is a Smalltalk library which allows Java code to be invoked from Smalltalk. It acts as a bridge between the world of Smalltalk objects and a Java Virtual Machine (JVM) where Java code is executing. >> >> If you want to know what can be done with JNIPort, see >> http://philemonworks.wordpress.com/2010/04/29/google-api-access-from-smallt… >> for an example. >> >> Installation instructions are on the Wiki at SqueakSource. See http://jniport.wikispaces.com/ for more information about JNIPort. >> >> The current state of the Pharo/Squeak version of JNIPort (as of 7 June 2010): >> â¢ Callbacks from Java to Smalltalk are not yet supported. >> â¢ In contrast to VisualWorks and Dolphin, JNIPort does not create ghost classes as wrappers for Java classes, but creates ârealâ classes which can be seen in the system browser. It also does not copy prototypes of CompiledMethods when a wrapper class or a Java class is created, because this causes VM failures in Pharo 1.0. Instead, methods are compiled from source code. This has a performance impact, of course. >> â¢ Another difference from the VisualWorks and Dolphin versions is that wrappers for Java methods without arguments donât have selectors ending with an awkward â_nullâ suffix. >> â¢ JNIPort has been developed and tested with Pharo 1.0 on Mac OS X 10.6.3. If it works in Squeak and on other operating systems has yet to be tested. >> â¢ I have briefly tested JNIPort with Pharo 1.1 beta 11367, but this needed some manual modifications of Alien â without them Alien causes problems in Pharo 1.1. >> â¢ In Pharo 1.1, starting a JVM needs 11 seconds vs. 4 seconds in Pharo 1.0. I donât know yet why. >> â¢ I donât have a Metacello configuration yet. >> >> The next steps will be: >> â¢ Adding support for callbacks from Java to Smalltalk. >> â¢ Testing it on more platforms. >> â¢ Reorganization of the documentation on the JNIPort wiki, and addition of Pharo/Squeak specific documentation similar to the documentation for the VisualWorks version. >> â¢ Release of JNIPort 2.0 for VisualWorks and Pharo/Squeak when everything is stable. This will be after the release of Pharo 1.1. >> >> If it works in Squeak 4.1 or on Linux or Windows, please let me know, especially if you had to do something which might be worth mentioning in the installation instructions. >> >> Have fun with JNIPort, and let me know if it works! >> >> Joachim Geidel >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

June 8, 2010

Alien for Squeak 4.1/Pharo 1.1?

by Joachim Geidel

I somehow managed to load Alien into both Squeak 4.1 and Pharo 1.1. You can see what I had to do in the installation instructions for JNIPort on SqueakSource. It's not for the faint of heart... ;-) In Squeak, this meant removing the Alien-Prereqs package and all Parser/Scanner/MethodNode changes, as they are redundant or obsolete in Squeak 4.1. I have a version of the Alien-Core Monticello package which loads cleanly in Squeak 4.1, if anybody is interested. However, this package does not load in Pharo 1.1 beta 11367 - some of the changes I removed still seem to be needed there. What are the plans for Alien? When will it be made available for Squeak 4.1 and Pharo 1.1? I am interested in this because I need Alien as the base for JNIPort, and I would like to at least run the JNIPort test suite on a stable version of Alien before officially releasing JNIPort 2.0. Joachim Geidel

June 8, 2010

Re: [Pharo-users] JNIPort preview for Pharo available on SqueakSource

by Tudor Girba

Indeed, we are very much interested in all this work! Doru On 8 Jun 2010, at 17:13, StÃ©phane Ducasse wrote: > Cool we are really busy but really interested. > We want to connect moose to java.... so what you are doing and also > johan is key for us. > > On Jun 7, 2010, at 7:07 PM, Joachim Geidel wrote: > >> I have made a preview release of JNIPort for Pharo/Squeak available >> on SqueakSource: >> http://www.squeaksource.com/JNIPort.html >> >> JNIPort is a Smalltalk library which allows Java code to be >> invoked from Smalltalk. It acts as a bridge between the world of >> Smalltalk objects and a Java Virtual Machine (JVM) where Java code >> is executing. >> >> If you want to know what can be done with JNIPort, see >> http://philemonworks.wordpress.com/2010/04/29/google-api-access-from-smallt… >> for an example. >> >> Installation instructions are on the Wiki at SqueakSource. See http://jniport.wikispaces.com/ >> for more information about JNIPort. >> >> The current state of the Pharo/Squeak version of JNIPort (as of 7 >> June 2010): >> â¢ Callbacks from Java to Smalltalk are not yet supported. >> â¢ In contrast to VisualWorks and Dolphin, JNIPort does not create >> ghost classes as wrappers for Java classes, but creates ârealâ >> classes which can be seen in the system browser. It also does not >> copy prototypes of CompiledMethods when a wrapper class or a Java >> class is created, because this causes VM failures in Pharo 1.0. >> Instead, methods are compiled from source code. This has a >> performance impact, of course. >> â¢ Another difference from the VisualWorks and Dolphin versions is >> that wrappers for Java methods without arguments donât have >> selectors ending with an awkward â_nullâ suffix. >> â¢ JNIPort has been developed and tested with Pharo 1.0 on Mac OS X >> 10.6.3. If it works in Squeak and on other operating systems has >> yet to be tested. >> â¢ I have briefly tested JNIPort with Pharo 1.1 beta 11367, but >> this needed some manual modifications of Alien â without them Alien >> causes problems in Pharo 1.1. >> â¢ In Pharo 1.1, starting a JVM needs 11 seconds vs. 4 seconds in >> Pharo 1.0. I donât know yet why. >> â¢ I donât have a Metacello configuration yet. >> >> The next steps will be: >> â¢ Adding support for callbacks from Java to Smalltalk. >> â¢ Testing it on more platforms. >> â¢ Reorganization of the documentation on the JNIPort wiki, and >> addition of Pharo/Squeak specific documentation similar to the >> documentation for the VisualWorks version. >> â¢ Release of JNIPort 2.0 for VisualWorks and Pharo/Squeak when >> everything is stable. This will be after the release of Pharo 1.1. >> >> If it works in Squeak 4.1 or on Linux or Windows, please let me >> know, especially if you had to do something which might be worth >> mentioning in the installation instructions. >> >> Have fun with JNIPort, and let me know if it works! >> >> Joachim Geidel >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

June 8, 2010

Re: [Pharo-users] JNIPort preview for Pharo available on SqueakSource

by StÃ©phane Ducasse

Cool we are really busy but really interested. We want to connect moose to java.... so what you are doing and also johan is key for us. On Jun 7, 2010, at 7:07 PM, Joachim Geidel wrote: > I have made a preview release of JNIPort for Pharo/Squeak available on SqueakSource: > http://www.squeaksource.com/JNIPort.html > > JNIPort is a Smalltalk library which allows Java code to be invoked from Smalltalk. It acts as a bridge between the world of Smalltalk objects and a Java Virtual Machine (JVM) where Java code is executing. > > If you want to know what can be done with JNIPort, see > http://philemonworks.wordpress.com/2010/04/29/google-api-access-from-smallt… > for an example. > > Installation instructions are on the Wiki at SqueakSource. See http://jniport.wikispaces.com/ for more information about JNIPort. > > The current state of the Pharo/Squeak version of JNIPort (as of 7 June 2010): > â¢ Callbacks from Java to Smalltalk are not yet supported. > â¢ In contrast to VisualWorks and Dolphin, JNIPort does not create ghost classes as wrappers for Java classes, but creates ârealâ classes which can be seen in the system browser. It also does not copy prototypes of CompiledMethods when a wrapper class or a Java class is created, because this causes VM failures in Pharo 1.0. Instead, methods are compiled from source code. This has a performance impact, of course. > â¢ Another difference from the VisualWorks and Dolphin versions is that wrappers for Java methods without arguments donât have selectors ending with an awkward â_nullâ suffix. > â¢ JNIPort has been developed and tested with Pharo 1.0 on Mac OS X 10.6.3. If it works in Squeak and on other operating systems has yet to be tested. > â¢ I have briefly tested JNIPort with Pharo 1.1 beta 11367, but this needed some manual modifications of Alien â without them Alien causes problems in Pharo 1.1. > â¢ In Pharo 1.1, starting a JVM needs 11 seconds vs. 4 seconds in Pharo 1.0. I donât know yet why. > â¢ I donât have a Metacello configuration yet. > > The next steps will be: > â¢ Adding support for callbacks from Java to Smalltalk. > â¢ Testing it on more platforms. > â¢ Reorganization of the documentation on the JNIPort wiki, and addition of Pharo/Squeak specific documentation similar to the documentation for the VisualWorks version. > â¢ Release of JNIPort 2.0 for VisualWorks and Pharo/Squeak when everything is stable. This will be after the release of Pharo 1.1. > > If it works in Squeak 4.1 or on Linux or Windows, please let me know, especially if you had to do something which might be worth mentioning in the installation instructions. > > Have fun with JNIPort, and let me know if it works! > > Joachim Geidel > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 8, 2010

Re: [Pharo-users] JNIPort preview for Pharo available on SqueakSource

by Mariano Martinez Peck

great work. Congratulations. I cc'ed pharo mailing list. cheers mariano On Mon, Jun 7, 2010 at 7:07 PM, Joachim Geidel <joachim.geidel(a)onlinehome.de > wrote: > I have made a preview release of JNIPort for Pharo/Squeak available on > SqueakSource: > http://www.squeaksource.com/JNIPort.html > > JNIPort is a Smalltalk library which allows Java code to be invoked from > Smalltalk. It acts as a bridge between the world of Smalltalk objects and a > Java Virtual Machine (JVM) where Java code is executing. > > If you want to know what can be done with JNIPort, see > > http://philemonworks.wordpress.com/2010/04/29/google-api-access-from-smallt… > for an example. > > Installation instructions are on the Wiki at SqueakSource. See > http://jniport.wikispaces.com/ for more information about JNIPort. > > The current state of the Pharo/Squeak version of JNIPort (as of 7 June > 2010): > > - Callbacks from Java to Smalltalk are not yet supported. > - In contrast to VisualWorks and Dolphin, JNIPort does not create ghost > classes as wrappers for Java classes, but creates ârealâ classes which can > be seen in the system browser. It also does not copy prototypes of > CompiledMethods when a wrapper class or a Java class is created, because > this causes VM failures in Pharo 1.0. Instead, methods are compiled from > source code. This has a performance impact, of course. > - Another difference from the VisualWorks and Dolphin versions is that > wrappers for Java methods without arguments donât have selectors ending with > an awkward â_nullâ suffix. > - JNIPort has been developed and tested with Pharo 1.0 on Mac OS X > 10.6.3. If it works in Squeak and on other operating systems has yet to be > tested. > - I have briefly tested JNIPort with Pharo 1.1 beta 11367, but this > needed some manual modifications of Alien â without them Alien causes > problems in Pharo 1.1. > - In Pharo 1.1, starting a JVM needs 11 seconds vs. 4 seconds in Pharo > 1.0. I donât know yet why. > - I donât have a Metacello configuration yet. > > > The next steps will be: > > - Adding support for callbacks from Java to Smalltalk. > - Testing it on more platforms. > - Reorganization of the documentation on the JNIPort wiki, and addition > of Pharo/Squeak specific documentation similar to the documentation for the > VisualWorks version. > - Release of JNIPort 2.0 for VisualWorks and Pharo/Squeak when > everything is stable. This will be after the release of Pharo 1.1. > > > If it works in Squeak 4.1 or on Linux or Windows, please let me know, > especially if you had to do something which might be worth mentioning in the > installation instructions. > > Have fun with JNIPort, and let me know if it works! > > Joachim Geidel > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >

June 7, 2010