October 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Smalltalk Interchange Format [was Xtreams : first embryonary port on Squeak]
by Nicolas Cellier Oct. 10, 2010

Oct. 10, 2010

Thanks Bill, some of the link on this page seem dead though... Nicolas 2010/10/10 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > FWIW, SIF might help you: > > Â http://www.pocketsmalltalk.com/sif/ > > I have put a lot of code through it in the past couple of years. > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Nicolas Cellier [nicolas.cellier.aka.nice(a)gmail.com] > Sent: Saturday, October 09, 2010 6:33 PM > To: The general-purpose Squeak developers list; Pharo Development; vwnc(a)cs.uiuc.edu > Subject: [Pharo-project] Xtreams : first embryonary port on Squeak > > So, I started a quick port of VW Xtreams to Squeak this evening. > Only the Xtreams-Core and the trivial Xtreams-Terminals (no > file/pipe/socket/pointer). > You'll find code at http://www.squeaksource.com/XTream. > My previous experimental Xtream project has been renamed SqueaXTream > to reduce confusion, but still sits in the same project. > Please find my report below. > > cheers > > Nicolas > > --------------------- REPORT Â --------------------- > > THE CONTENTS: > > This first port is made of 3 packages > - Xtreams-Core > - Xtreams-Terminals > - Xtreams-VWCompatible > Plus 2 tests > - Xtreams-CoreTests > - Xtreams-TerminalsTests > Please notice I removed one hyphen from test package names for MC compatibility. > > THE PROCEDURE: > > I didn't use FileOut30 not any more advanced tool, but just a simple > copy/paste strategy. > This gave me a chance to do a fast review of code. > For porting the future evolutions of VW Xtreams, more advanced tools > will be necessary, the manual approach does not scale. > > THE MODIFICATIONS: > > The changes I made are quite restricted, which indicates that Xtreams > is not that hard to port. > Main changes are due to lack of namespace in Squeak: > - I added a XT prefix to every Xtreams classes (no Namespace in Squeak) > - I added XTPools, a SharedPool for holding the single Xtreams > namespace variable DefaultBufferSize > - I transformed class SharedVariables into class variables and added > proper class side initialization for these in XTWriteStream > > For the rest, I tried to not change Xtreams contents. but rather did > implement VW compatible messages when possible in the > Xtreams-VWCompatible package when they did not exist in Squeak. > These message are a full rewrite and are also released under MIT license. > The few exceptions are: > - I modified originator -> self originator in XTIncomplete. > - I changed the senders of #newInFixedSpace: to rather send an #error: > 'not implemented in Squeak' in XTRecyclingBuffer > - I replaced #waitIfCurtailedSignal/#signal with a #critical: section > in XTRecyclingBuffer > - I replaced Â Core.Timer after:do: with self after:do: in Xtreams-CoreTests > > A DISCUSSION OF TECHNICAL DETAILS: > > I first attempted to replace #growToAtLeast: with #grownBy: because > Squeak become: is notoriously inefficient. > But obviously, this did not work, the tests rely on destination > preserving its identity. > This clearly is going to degrade micro benchmarks when the destination > collection capacity is not well adjusted in advance. > I think we should discuss this particular point. Is identity > preservation absolutely required, or just convenient ? > > THE STATUS OF TESTS: > > Tests do not all pass. There seems to be a bug in Squeak > #replace:from:to:with: when the replacement is the collection itself, > moved to the right (this is with a COG VM). > > THE FUTURE: > > I will probably continue porting with reduced activity, so I invite > any interested person to help. Right now, the project is world > writeable, code commited here falling under MIT license. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

2 1

[Pharo-project] [OT] database choices
by Schwab,Wilhelm K Oct. 10, 2010

Oct. 10, 2010

Just learned about this one: http://mariadb.org/index.html It sounds like the old guard of MySQL is coalescing around it. It's up to you to decide whether that is true, and if so, whether it is a good thing.

2 1

Re: [Pharo-project] Help request on Xtreams tests with forked process [ was Xtreams : first embryonary port on Squeak ]
by Nicolas Cellier Oct. 10, 2010

Oct. 10, 2010

Hi Bill, I see, you're helping me to help myself :) What I was looking at was more like a free lunch ;) Nicolas 2010/10/10 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > Nicolas, > > #fork in a test? Â Do you mean like the code below? Â The thread running the test waits on something signaled toward the end of the forked thread. > > If you want a watchdog timer, you could fork another thread that waits on a delay, sets an error flag (best to use a shared queue or a mutex to avoid weirdness) and then signals the test semaphore. Â You might also want to use #ifCurtailed: to set an error flag and wrap that with #ensure: to signal the semaphore. Â You don't necessarily need to be perfect about signaling the semaphore because failure to do so is not much different from your test going into an infinite loop (actually more benign because the stack isn't growing); you'll realize it, break, and figure out what didn't happen or at least "that it didn't" and try again forewarned. > > Does that help? > > Bill > > > testLocalServerAndClient > Â Â Â Â "11-09 - try a server and a client in the same image." > > Â Â Â Â Â Â Â Â | server port client serverSocket serverSocketStream text thread done read | > > Â Â Â Â port := 4900. > Â Â Â Â done := Semaphore new. > > Â Â Â Â "11-09 - gag the prompter below" > Â Â Â Â serverSocket := nil. > > Â Â Â Â server := ConnectionQueue portNumber:port queueLength:5. > Â Â Â Â [ > Â Â Â Â Â Â Â Â client := SocketStream openConnectionToHostNamed:'localhost' port:port. > Â Â Â Â Â Â Â Â [ serverSocket isNil ] whileTrue:[ > Â Â Â Â Â Â Â Â Â Â Â Â serverSocket := server getConnectionOrNil. > Â Â Â Â Â Â Â Â ]. > > Â Â Â Â Â Â Â Â serverSocketStream := SocketStream on:serverSocket. > Â Â Â Â Â Â Â Â text := 'Long live Tux!'. > Â Â Â Â Â Â Â Â serverSocketStream nextPutAll:text; flush. > > Â Â Â Â Â Â Â Â "11-09 - this hung up w/o the thread. > Â Â Â Â Â Â Â Â 11-09 - as you were; the problem was a lack of #flush on the send side, so there was > Â Â Â Â Â Â Â Â nothing for the client side to read." > Â Â Â Â Â Â Â Â thread := [ > Â Â Â Â Â Â Â Â Â Â Â Â read := client nextMany:text size. > Â Â Â Â Â Â Â Â Â Â Â Â done signal. > Â Â Â Â Â Â Â Â ] forkAt:Processor userBackgroundPriority. > Â Â Â Â Â Â Â Â thread name:'READ'. > > Â Â Â Â Â Â Â Â done wait. > Â Â Â Â Â Â Â Â self should:[ read = text ]. > Â Â Â Â Â Â Â Â Transcript nextPutAll:'Just to make the point, we read: '; nextPutAll:read; cr; flush. > > Â Â Â Â ] ensure:[ > Â Â Â Â Â Â Â Â server destroy. > Â Â Â Â Â Â Â Â serverSocketStream close. > Â Â Â Â Â Â Â Â client close. > Â Â Â Â ]. > > Â Â Â Â "11-09 - no prompts" > Â Â Â Â serverSocket := serverSocket. > Â Â Â Â client := client. > Â Â Â Â serverSocketStream := serverSocketStream. > Â Â Â Â thread := thread. > > Â Â Â Â " > Â Â Â Â Â Â Â Â NetworkSmokeTestCase prod:#testLocalServerAndClient. > Â Â Â Â " > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Nicolas Cellier [nicolas.cellier.aka.nice(a)gmail.com] > Sent: Sunday, October 10, 2010 7:05 AM > To: The general-purpose Squeak developers list > Cc: Pharo Development > Subject: Re: [Pharo-project] [squeak-dev] Xtreams : first embryonary port on Â Â Squeak > > 2010/10/10 Levente Uzonyi <leves(a)elte.hu>: >> On Sun, 10 Oct 2010, Nicolas Cellier wrote: >> >>> >>> THE STATUS OF TESTS: >>> >>> Tests do not all pass. There seems to be a bug in Squeak >>> #replace:from:to:with: when the replacement is the collection itself, >>> moved to the right (this is with a COG VM). >> >> #replace:from:to:with: is not supposed to work for moves. IIRC the primitive >> version uses memcpy (or strncpy), so moving to the left works just because >> the undelying C function supports it. I used to (ab)use this feature though. >> >> >> Levente >> > > OK, since we use memcpy rather than memmove in Squeak VM, I > implemented the trivial work around - move through a motionBuffer > temporary copy. > > I now have a single test failing, > XTCollectionWriteStream>>#testReadWriteLargeAmount and this must be > due to my #after:do: simplistic implementation. > Messing with #fork in SUnit TestCase is tricky, and I need help on this point. > > Nicolas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

2 1

[Pharo-project] Compiler pedantic about ifNotNil: argument
by Nicolas Cellier Oct. 10, 2010

Oct. 10, 2010

The compiler uselessly insist on #ifNotNil: argument being a zero/one arg block. Thus we cannot write this xtream sentence process ifNotNil: #terminate. When the argument is not a block, Compiler should avoid inlining and just send a normal message. cheers Nicolas

5 9

[Pharo-project] little bug in OB running tests
by Mariano Martinez Peck Oct. 10, 2010

Oct. 10, 2010

Hi Lukas. A lot of times, I run tests with cmd + t in OB and the test fails (mostly becuase I like doing TDD). When I press proceed and the test passes (green), the little point on the left of the method in OB, isn't painted with green color as it does when the test directly passes (withput a failure in the middle). Thanks Mariano

2 1

[Pharo-project] Symbol>>cull:
by Nicolas Cellier Oct. 10, 2010

Oct. 10, 2010

We recently added #value: to Symbol to be able to use it in place of a one arg block. (1 to: 10) select: #even. It would be logical to add #cull: too, xtreams tests use this for example: output write: #[ 1 2 3 4 5 6 7 8 9 ]. self assert: ((input rejecting: #even) read: 5) = #[ 1 3 5 7 9 ] Any objection to add it in core ? (otherwise i will add it to Xtreams-VWCompatible) Nicolas

2 1

Re: [Pharo-project] Compiler pedantic about ifNotNil: argument
by StÃ©phane Ducasse Oct. 10, 2010

Oct. 10, 2010

On Oct 10, 2010, at 3:17 PM, Igor Stasenko wrote: > On 10 October 2010 16:13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> personnally I do not like this form >> What does it do? >> >>> process ifNotNil: #terminate. >> > > here the test case for it: > > | process answer | > > process := Object new. > > answer := process ifNotNil: #terminate. > > self assert: answer == #terminate. all that to avoid to have ifNotNil: [#terminate] I would not change the ifNotNil: for that. But make the compiler smarter Stef > > >> >> for me it means passes the symbol #terminate as argument to the method ifNotNil: >> If it has a more magical behavior then I do not know it. >> >> Stef >> >> >>> The compiler uselessly insist on #ifNotNil: argument being a zero/one arg block. >>> Thus we cannot write this xtream sentence >>> >>> process ifNotNil: #terminate. >>> >>> When the argument is not a block, Compiler should avoid inlining and >>> just send a normal message. >>> >>> cheers >>> >>> Nicolas >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Glamour breaks settings browser on Pharo 1.1.1
by Esteban Lorenzano Oct. 10, 2010

Oct. 10, 2010

Hi, I'm loading Glamour into a PharoDev 1.1.1 Gofer project repository: 'http://www.squeaksource.com/Glamour'; load: 'Glamour' version: '2.0-beta.7'. and then try to open the settings browser... it raises a DNU Cheers, Esteban

2 3

Re: [Pharo-project] [vwnc] Xtreams : first embryonary port on Squeak
by Nicolas Cellier Oct. 10, 2010

Oct. 10, 2010

2010/10/10 Michael Lucas-Smith <michael.lucassmith(a)gmail.com>: >> >> I first attempted to replace #growToAtLeast: with #grownBy: because >> Squeak become: is notoriously inefficient. >> But obviously, this did not work, the tests rely on destination >> preserving its identity. >> This clearly is going to degrade micro benchmarks when the destination >> collection capacity is not well adjusted in advance. >> I think we should discuss this particular point. Is identity >> preservation absolutely required, or just convenient ? > > Which tests? I'd be in favor of removing that assumption. > > Michael > This is in: CollectionReadingWritingTest>>setUp | buffer | buffer := XTElasticBuffer on: ByteArray new. input := buffer reading. output := buffer writing. The expectation is that the buffer will be shared between input and output. If output modifies a copy of buffer, then the tests fail (input is empty or partial or too long if WriteStream>>#close did not perform a #become: ) Nicolas

1 0

[Pharo-project] Newbie question: Connection to SQLite DB
by nullPointer Oct. 10, 2010

Oct. 10, 2010

IÂ´m cannot connect a sample SQLite DB. IÂ´m sure need some steps but I donÂ´t know exactly. Really I have alway problems when I try execute some external to Smalltalk image. Exists a document with global information of that? I did install SQueakDBX (with problems for #and:and:and: deprecated method of boolean), but the system launch a error when I try create and open the connection to DB. Looking in SqueakSource appears too a SQLite project ( SQLite3-Core and SQLite3-Tests ) but I get the same error... I understand the problem is for FFI... but I donÂ´t understand what is the cause... Is needed something more for run FFI? Thanks for the help. -- View this message in context: http://forum.world.st/Newbie-question-Connection-to-SQLite-DB-tp2954195p295… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 11