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

Re: [Pharo-project] Creating temporary classes for testing

by Alexandre Bergel

This is something that I often need. I have always addressed this as follows: Added a 'classes' instance variable in my unit test. Added a bunch of methods such as: createClassNamed: aSymbol superclass: aSuperclass instVarNames: instVarNames | cls | cls := aSuperclass subclass: aSymbol instanceVariableNames: instVarNames classVariableNames: '' poolDictionaries: '' category: 'Generated'. self classes add: cls. ^ cls Then in the teardown I have something like: tearDown super tearDown. classes ifNotNil: [:clss | clss do: #removeFromSystem ]. You may also want to remove the empty category in the tearDown. Cheers, Alexandre On 9 Dec 2010, at 14:50, Sean P. DeNigris wrote: > > > Noury Bouraqadi-2 wrote: >> >> -You want to test something related to classes, and in this case you can >> use the SUnit extension I introduced a while ago ClassFactoryForTestCase. >> It's part of the core image. >> > > Cool, that's it exactly. > > Now I have two new questions: > * What if ClassFactoryForTestCase used the separate-SystemDictionary > approach? Wouldn't you only need to clean up the logs and the classes would > get gc-ed (even if cleanup was never called)? > * Is my OP correct that it is safe to do what I was doing i.e. no effect to > the system (except maybe the doit in the changes)? (I may have another > application for it) > > Thanks. > Sean > -- > View this message in context: http://forum.world.st/Creating-temporary-classes-for-testing-tp3080408p3080… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 9, 2010

Re: [Pharo-project] Creating temporary classes for testing

by Sean P. DeNigris

Noury Bouraqadi-2 wrote: > > -You want to test something related to classes, and in this case you can > use the SUnit extension I introduced a while ago ClassFactoryForTestCase. > It's part of the core image. > Cool, that's it exactly. Now I have two new questions: * What if ClassFactoryForTestCase used the separate-SystemDictionary approach? Wouldn't you only need to clean up the logs and the classes would get gc-ed (even if cleanup was never called)? * Is my OP correct that it is safe to do what I was doing i.e. no effect to the system (except maybe the doit in the changes)? (I may have another application for it) Thanks. Sean -- View this message in context: http://forum.world.st/Creating-temporary-classes-for-testing-tp3080408p3080… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 9, 2010

Re: [Pharo-project] Why is FileStream writing almost an order of a magnitude slower than reading ?

by Sven Van Caekenberghe

Levente, On 08 Dec 2010, at 13:03, Levente Uzonyi wrote: > I don't get how #streamContents: could be used to send #flush. That's a method of SequenceableCollection IIRC. Yeah, you're right: I stand corrected, this is not related. I tried adding an #on:do: modeled after #fileNamed:do: to ensure that #flush is called, which is more elegant IMHO: [ FileStream fileNamed: '/tmp/numbers.txt' do: [ :fileStream | ZnBufferedWriteStream on: fileStream do: [ :bufferedStream | 100000 timesRepeat: [ bufferedStream print: 100 atRandom; space ] ] ] ] timeToRun. > SocketStream is unrelated here, because it doesn't write to files and buffering was always implemented in it AFAIK. I think it is relevant: it proves that people can perfectly live with output buffering. Can you give an example of which code would break (so needs to call #flush) with output buffering ? Would there be many cases ? Sven

Dec. 9, 2010

Re: [Pharo-project] Where does Regex-Core and friends live

by Alexandre Bergel

Ok, it makes sense Alexandre On 9 Dec 2010, at 13:47, Dale Henrichs wrote: > On 12/08/2010 06:21 PM, Alexandre Bergel wrote: >> hi Dale! >> >> I do not know about your need. But personally, if I have to deal with non trivial parsing, I will use PetitParser. >> Lukas made a tutorial last week and I am convinced. >> >> Cheers, >> Alexandre >> >> >> On 8 Dec 2010, at 20:57, Dale Henrichs wrote: >> >>> I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository. >>> >>> In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates. >>> >>> I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ... >>> >>> Dale >>> >> > I'm interested in terms of maintaining Pharo compatibility ... many of the GLASS developers develop in Pharo and deploy in GemStone and I am trying to get in the habit of using the same packages that are loaded into Pharo (where possible/practical) so that the bugfixes and updates can be shared without too much trouble ... > > Dale -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 9, 2010

Re: [Pharo-project] Issue 3396 in pharo: System Change Notification broken

by pharo＠googlecode.com

Updates: Summary: System Change Notification broken Comment #2 on issue 3396 by renggli: System Change Notification broken http://code.google.com/p/pharo/issues/detail?id=3396 (No comment was entered for this change.)

Dec. 9, 2010

Re: [Pharo-project] Where does Regex-Core and friends live

by Dale Henrichs

On 12/08/2010 11:44 PM, Lukas Renggli wrote: >> I am porting the latest Regex to GemStone and in the interest of Pharo >> compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo >> repository. > > The latest code is in<http://source.lukas-renggli.ch/unsorted/>. > > It is a full port of the latest code from VisualWorks + various > critical bug fixes. > > Except for the packaging (which is identical to VisualWorks), it > should be the same as the code in Pharo. > > Lukas > My first choice is to use the packages that are loaded into Pharo, since I am trying to maintain Pharo compatibility, so I want the packaging changes as well ... Dale

Dec. 9, 2010

[Pharo-project] System Change Notification Broken

by Lukas Renggli

I wanted to draw the attention to http://code.google.com/p/pharo/issues/detail?id=3396 The system change notification service is kind of critical for everything. Any idea why it doesn't work anymore in the latest system? Lukas -- Lukas Renggli www.lukas-renggli.ch

Dec. 9, 2010

Re: [Pharo-project] Issue 3396 in pharo: Change Notification in Monticello Browser is broken

by pharo＠googlecode.com

Comment #1 on issue 3396 by renggli: Change Notification in Monticello Browser is broken http://code.google.com/p/pharo/issues/detail?id=3396 Note that also the Test Runner and OB does not update anymore. So there seems to be something very serious broken.

Dec. 9, 2010

Re: [Pharo-project] Where does Regex-Core and friends live

by Dale Henrichs

On 12/08/2010 11:50 PM, Lukas Renggli wrote: >> I've got a GemSource repository, but I'm actually hoping (haven't run tests >> yet:) that I will be able to use Regex-Core without making any >> GemStone-specific changes ... > > That's unlikely, because the code makes quite some absolute stream > positioning like aStream position = 0, aStream position = aStream > size, etc. > > Lukas > Lukas, I've pulled down the Ansi compatible stream implementations (where position has been fixed) that I was using for Grease and all of the tests pass, so unless there are some corner cases I'm missing (always a possibility) GemStone-specific changes aren't needed... Dale

Dec. 9, 2010

Re: [Pharo-project] Where does Regex-Core and friends live

by Dale Henrichs

On 12/08/2010 06:21 PM, Alexandre Bergel wrote: > hi Dale! > > I do not know about your need. But personally, if I have to deal with non trivial parsing, I will use PetitParser. > Lukas made a tutorial last week and I am convinced. > > Cheers, > Alexandre > > > On 8 Dec 2010, at 20:57, Dale Henrichs wrote: > >> I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository. >> >> In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates. >> >> I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ... >> >> Dale >> > I'm interested in terms of maintaining Pharo compatibility ... many of the GLASS developers develop in Pharo and deploy in GemStone and I am trying to get in the habit of using the same packages that are loaded into Pharo (where possible/practical) so that the bugfixes and updates can be shared without too much trouble ... Dale

Dec. 9, 2010