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

Re: [Pharo-users] Writing extensions

by Mariano Martinez Peck

Hi Bob and welcome. There are two possibiities I know to write/communicate to C: - The FFI plugin is intended to call external libraries from Smalltalk http://wiki.squeak.org/squeak/1414 http://forum.world.st/FFI-Documentation-td2225148.html#a2225148 - Write your own VM primitives http://wiki.squeak.org/squeak/356 http://wiki.squeak.org/squeak/3336 http://wiki.squeak.org/squeak/6102 Probably there are much more links, but maybe this is enough to remember you what you used. Let us know Mariano On Mon, Jun 14, 2010 at 9:02 PM, Bob Cowdery <bob(a)bobcowdery.plus.com>wrote: > Hi all, > > I played with Squeak about 4 years ago and I built some extensions in C. > I would like to do the same again with Pharo and I have a big lump of C > I would like to interface to. I can't actually remember what I did > before and can't seem to find the tutorial I used. Could somebody point > me in the right direction please. > > Thanks > Bob > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

June 21, 2010

Re: [Pharo-users] Glorp & PostgresV2

by Sven Van Caekenberghe

Mariano, I made my own loader and patches packages for loading Glorp+PostgresV2 into Pharo 1.1rc2. Both can be found at http://www.squeaksource.com/ADayAtTheBeach GlorpPostgreSQLPharoLoader-SvenVanCaekenberghe.3.mcz GlorpPostgreSQLPharoPatches-SvenVanCaekenberghe.1.mcz All PostgresV2 tests succeed, as do all GlorpTest-DBTests. The GlorpTest package has the following result: 844 run, 838 passes, 0 expected failures, 4 failures, 2 errors, 0 unexpected passes Failures: GlorpSelectCommandTest>>#testExecute GlorpUnitOfWorkTest>>#testRollbackOneToManyAfterAdd GlorpDateTest>>#testDate GlorpRowMapForMementosCollectionTest>>#testRBSmallDictionary Errors: GlorpManyToManyDBTest>>#testReadNodeAndDeleteChildWithSaveAndContinue GlorpObjectMappedToImaginaryTableTest>>#testReadBackEntireExample My own code runs fine though. I hope you consider my patches, thanks, Sven BTW: the original #timestampWithTimezoneConverter simply could never work: it expects a +/- sign inbetween the timezone's offset's hour and minute fields ! it falls out of the tests because only timestamo without timezones are used.

June 14, 2010

Writing extensions

by Bob Cowdery

Hi all, I played with Squeak about 4 years ago and I built some extensions in C. I would like to do the same again with Pharo and I have a big lump of C I would like to interface to. I can't actually remember what I did before and can't seem to find the tutorial I used. Could somebody point me in the right direction please. Thanks Bob

June 14, 2010

Re: [Pharo-users] [SPAM] Re: WebClient

by Sven Van Caekenberghe

StÃ©phane, On 11 Jun 2010, at 23:09, StÃ©phane Ducasse wrote: > Hi sven > >> Hi, >> >> Andreas Raab's 'new' WebClient/WebServer seems quite nice, as he says himself: >> >> As a result, we now have what I think is a pretty decent HTTP server and client implementation for Squeak 4.1 and hopefully we can nuke HTTPSocket sometime soon. WebClient is superior in every respect. >> >> Is this something that will / should fit seamlessly into Pharo ? Or even become preinstalled ? > > could be but not at the price to have concatenation of string and numbers. > So this means that somebody would have to do a pass on the code and produce a pharo version that squeakers may want or not. I went over the code and produced a version of WebClient-Core (and WebClient-Test) that passes all units tests in Pharo 1.1 rc 2: Filename: WebClient-Core-SvenVanCaekenberghe.24.mcz Author: Sven Van Caekenberghe Timestamp: 14 June 2010 4:24:21 pm UUID: 92b7f407-8df1-4472-962b-45d99f2364b8 Ancestors: WebClient-Core-ar.23.mcz Filename: WebClient-Tests-SvenVanCaekenberghe.12.mcz Author: Sven Van Caekenberghe Timestamp: 14 June 2010 4:25 pm UUID: f495c2cd-54bb-42a9-a6d7-f380cd656f3f Ancestors: WebClient-Tests-ar.11.mcz Both at http://www.squeaksource.com/ADayAtTheBeach. The only remaining method needed from the old WebClient-Pharo package is String#squeakToUtf8 squeakToUtf8 "Convert the receiver into a UTF8-encoded string" ^self convertToWithConverter: UTF8TextConverter new. There are only 4 callers so I could change that as well, should I ? I checked the references to UTF8TextConverter and it feels as if you don't want a method like #squeakToUtf8 (apart from the name ;-) >> I didn't try his ConfigurationOfWebClient since the last version was unreadable and it seemed like an experiment, while his textual explanation was easy to follow. >> >> To load it into and to make the unit tests run in Pharo 1.0 I had to make a couple of fixes (to WebCookie#printOn: and WebServer class#serverString). Who should I sent these changes to ? > > to andreas? > may be ask him if he wants to have a version working also for pharo but without String#, override I will contact Andreas directly once I know your position on the last remaining item. Sven BTW, Is there a way to make a (old school) ChangeSet (or even another 'patch' package) out of the differences between versions in Monticello ? >> But even then 1 unit test failed (#testServerDestroy). >> >> Furthermore, some the changes in his package WebClient-Pharo seem a bit dangerous, especially a modification to SocketStream#peek (and the failed test was doing a peek) and an override of String#, some others are unneccessary as far as I can see. >> >> Sven >> >> -- >> Sven Van Caekenberghe - mailto:sven@beta9.be >> Beta Nine - software engineering - http://www.beta9.be >> .Mac - svc(a)mac.com - http://homepage.mac.com/svc >> >> >> >> _______________________________________________ >> 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

June 14, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.1-11400-rc1dev10.06.1

by laurent laffont

On Sun, Jun 13, 2010 at 11:19 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi folks. There is a new Pharo 1.1 rc2 image for beta testing. It is based > in PharoCore rc2 11400. > Help menu is gone ? Was fixed in http://code.google.com/p/pharo/issues/detail?id=2442 Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > A little remark is that this is the first release candidate, not the second > one. There was a problem when building the PharoCore rc1 and thus, we used > PharoCore RC2. To be concistent we call it Pharo 1.1 rc2 to this image. > > We are getting closer to the stable release of Pharo 1.1 so we would really > appreaciate any kind of feedback. Use it, load your packages and > applications, run tests, etc. > > The download link is: > https://gforge.inria.fr/frs/download.php/27159/Pharo-1.1-11400-rc2dev10.06.… > > Cheers > > Mariano > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >

June 14, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.1-11400-rc1dev10.06.1

by StÃ©phane Ducasse

mariano I suggest that we remove the newinspector from the dev tools because this is still really strange to use it. Stef On Jun 13, 2010, at 11:19 PM, Mariano Martinez Peck wrote: > Hi folks. There is a new Pharo 1.1 rc2 image for beta testing. It is based in PharoCore rc2 11400. > > A little remark is that this is the first release candidate, not the second one. There was a problem when building the PharoCore rc1 and thus, we used PharoCore RC2. To be concistent we call it Pharo 1.1 rc2 to this image. > > We are getting closer to the stable release of Pharo 1.1 so we would really appreaciate any kind of feedback. Use it, load your packages and applications, run tests, etc. > > The download link is: https://gforge.inria.fr/frs/download.php/27159/Pharo-1.1-11400-rc2dev10.06.… > > Cheers > > Mariano > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 14, 2010

[BetaTesting] [ANN] Pharo-1.1-11400-rc1dev10.06.1

by Mariano Martinez Peck

Hi folks. There is a new Pharo 1.1 rc2 image for beta testing. It is based in PharoCore rc2 11400. A little remark is that this is the first release candidate, not the second one. There was a problem when building the PharoCore rc1 and thus, we used PharoCore RC2. To be concistent we call it Pharo 1.1 rc2 to this image. We are getting closer to the stable release of Pharo 1.1 so we would really appreaciate any kind of feedback. Use it, load your packages and applications, run tests, etc. The download link is: https://gforge.inria.fr/frs/download.php/27159/Pharo-1.1-11400-rc2dev10.06.… Cheers Mariano

June 13, 2010

Re: [Pharo-users] Priority of WeakArray finalizationProcess

by StÃ©phane Ducasse

On Jun 13, 2010, at 10:32 AM, Joachim Geidel wrote: > Am 12.06.10 21:51 schrieb StÃ©phane Ducasse: >> thanks for this report. >> Yes if you can add a bug report this would be great. >> >> Stef >> >> On Jun 12, 2010, at 9:16 PM, Joachim Geidel wrote: >> >>> While testing JNIPort on Pharo 1.0 and Pharo 1.1, I noticed that in Pharo >>> 1.0, a JVM (a wrapper object for the Java Virtual Machine) could be >>> initialized in ca. 4 seconds, while this needed 11 to 12 seconds in Pharo >>> 1.1. > > http://bugs.squeak.org/view.php?id=7546 > 0007546: WeakRegistry deadlock during finalization > > http://code.google.com/p/pharo/issues/detail?id=2551 > Issue 2551: Performance degradation of WeakRegistry in Pharo 1.1 > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

June 13, 2010

Re: [Pharo-users] Priority of WeakArray finalizationProcess

by Joachim Geidel

Am 12.06.10 21:51 schrieb StÃ©phane Ducasse: > thanks for this report. > Yes if you can add a bug report this would be great. > > Stef > > On Jun 12, 2010, at 9:16 PM, Joachim Geidel wrote: > >> While testing JNIPort on Pharo 1.0 and Pharo 1.1, I noticed that in Pharo >> 1.0, a JVM (a wrapper object for the Java Virtual Machine) could be >> initialized in ca. 4 seconds, while this needed 11 to 12 seconds in Pharo >> 1.1. http://bugs.squeak.org/view.php?id=7546 0007546: WeakRegistry deadlock during finalization http://code.google.com/p/pharo/issues/detail?id=2551 Issue 2551: Performance degradation of WeakRegistry in Pharo 1.1

June 13, 2010

Re: [Pharo-users] [squeak-dev] Priority of WeakArray finalizationProcess

by Joachim Geidel

Am 12.06.10 21:47 schrieb Levente Uzonyi: > On Sat, 12 Jun 2010, Joachim Geidel wrote: >> I am not sure if changing the priority of the finalizationProcess could >> possibly break something, and I also do not yet understand why changing the >> priority makes such a big difference both in Squeak and Pharo. > > I think normal processes (with priority 40) could starve the finalization > process if it's priority were <= 40 (#systemBackgroundPriority is 20). That's true, I hadn't thought of that. >> How should this issue be handled? Should I add this as issues to the bug >> tracking tools for Pharo and Squeak respectively? > > I uploaded a fix to the Inbox: Collections-ul.362. If you're using a Trunk > image, just update it and load this package to your image. If you're using > a stock 4.1 image, then the easiest way to get the fix, is to add the > following line to the end of WeakKeyDictionary >> #finalizeValues > > cleanUpAfterRemove ifTrue: [ self fixCollisionsFrom: array size ] > > If you have the time, please check if this fixes the issue for Squeak. Unfortunately, this doesn't help with the deadlock issue. Cheers, Joachim Geidel

June 13, 2010