Squeak-dev June 2010

squeak-dev@lists.squeakfoundation.org

96 participants
269 discussions

regex
by Casimiro de Almeida Barreto 07 Jun '10

07 Jun '10

Btw, in my last e-mail I meant something simpler than: | mx0 mx1 str oc | Transcrit clear. mx0 := RxMatcher forString: '(\d+)\s(\d\d)/(\d\d)/(\d\d\d\d)\s((\d+\s)+)(\d+)'. mx1 := RxMatcher forString: '(\d+)\s'. str := '1 27/05/1963 10 22 31 01 06 04 19 10 111'. (mx0 matches: str) ifFalse: [ Transcript show: 'mx0 failed to match: ',str; cr ] ifTrue: [ Transcript show: 'Identified ',mx0 subexpressionCount asString,' subexpressions.'; cr. Transcript show: 'Id: ',(mx0 subexpression: 2); cr. Transcript show: 'Date: ',(mx0 subexpression: 3),'/',(mx0 subexpression: 4),'/',(mx0 subexpression: 5); cr. Transcript show: 'Numbers: ',(mx0 subexpression: 6); cr. Transcript show: 'Acct: ',(mx0 subexpression: 8); cr. oc := mx1 matchesIn: (mx0 subexpression: 6). oc isNil ifTrue: [ Transcript show: 'mx1 failed to match: ',(mx0 subexpression: 6); cr ] ifFalse: [ 1 to: oc size do: [ :i | Transcript show: 'Nb(',i asString,') = ',(oc at: i); cr ]]]. Which is just too much text for little action...

1 0

Help with Regex
by Casimiro de Almeida Barreto 07 Jun '10

07 Jun '10

Hello, I'm facing the following problem: I have to extract patterns from a variable length expression. The form of the expression in itself is very simple: '20 31 64 33 99 12 32 11 44 16 ... 99 41' Meaning I've sequences of two digits separated by spaces. I just want to extract it using a "one pass regex". | rgx | rgx := RxMatcher forString: '...' But it seems that VBRegex has no recursion... If I want to have something like: rgx subexpression: 2 -> 20 rgx subexpression: 3 -> 31 ... rgx subexpression: n -> 41 what's the simplest way of doing that in one pass?

1 0

[ANN] Maui 1.2 release 1
by Chris Muller 07 Jun '10

07 Jun '10

In conjunction with the release of Squeak 4.1, I have made a new release of Maui that works with 4.1 and will be supported on that platform going forward. Maui is a user-interface builder for Squeak with a goal of _quickly_ producing effective drag-and-drop user-interfaces without having to write any code (although interfaces are also easily created via code). When used in conjunction with MaSarPackage (to announced shortly), applications can be easily deployed to SqueakMap that include the designers Maui-based user-interface. Maui is the framework I use exclusively for internal UI's at my company. Obviously I like it because I designed it to conform to my principles of an effective UI. However, a naked-objects type of user-interface will not be suitable for many situations or tastes. My teammates seem to be liking it, although they are polite. Nonetheless, it can be quite useful to have in the image for "quick and dirty" but useful image tools that just aren't easy to do any other way.. To use, in a standard Squeak 4.1 image, open SqueakMap, find Maui, install "1.2r1". To build a UI immediately, try dragging "Association" out of the browser onto the desktop. That's the Association class on the desktop, so drag the *class-side* constructor, #key:value: onto it... Your first Maui UI. I would have liked, of course, to release this with a bunch of "content" to entertain you. But given my large agenda, short resources, and the relatively low response to 1.1, I would like to try to get more mileage out of the original pdf document available on the swiki, into which I did put quite a bit of work into explaining Maui. Comments or questions about this 1.2 are very welcome. - Chris

4 6

FFI GSoC Project
by Dmitry Matveev 07 Jun '10

07 Jun '10

Hello, My name is Dmitry Matveev, I am a GSoC 2010 student. I am working on the project named "Progress Towards a Cross-Dialect Smalltalk FFI" (http://gsoc2010.esug.org/projects/ffi). I've read the CObject/Alien documentation and I've outlined the major FFI components. Please see my report and thoughts in the attached proposal. I want to port the GNU Smalltalk's CObject to the Squeak. Any comments are welcomed. Thanks! Dmitry

1 0

The Inbox: Multilingual-HenrikSperreJohansen.120.mcz
by commits＠source.squeak.org 07 Jun '10

07 Jun '10

A new version of Multilingual was added to project The Inbox: http://source.squeak.org/inbox/Multilingual-HenrikSperreJohansen.120.mcz ==================== Summary ==================== Name: Multilingual-HenrikSperreJohansen.120 Author: HenrikSperreJohansen Time: 7 June 2010, 3:06:29.846 pm UUID: 1a25b181-922c-425c-9565-d9be11d3cf3b Ancestors: Multilingual-ar.119 UTF16TextConverter's latin1Encoding uses default byte order, needs to change if byteorder is swapped. =============== Diff against Multilingual-ar.119 =============== Item was added: + ----- Method: UTF16TextConverter>>swapLatin1EncodingByteOrder (in category 'private') ----- + swapLatin1EncodingByteOrder + latin1Encodings := latin1Encodings collect: [:each | each reverse]! Item was changed: ----- Method: UTF16TextConverter>>useLittleEndian: (in category 'accessing') ----- useLittleEndian: aBoolean + aBoolean = self useLittleEndian ifFalse: [self swapLatin1EncodingByteOrder]. - useLittleEndian := aBoolean. !

1 0

The Inbox: MultilingualTests-HenrikSperreJohansen.10.mcz
by commits＠source.squeak.org 07 Jun '10

07 Jun '10

A new version of MultilingualTests was added to project The Inbox: http://source.squeak.org/inbox/MultilingualTests-HenrikSperreJohansen.10.mcz ==================== Summary ==================== Name: MultilingualTests-HenrikSperreJohansen.10 Author: HenrikSperreJohansen Time: 7 June 2010, 3:05:36.384 pm UUID: 5cfa2572-27cc-4dbc-8eea-1ac0ccfe13ef Ancestors: MultilingualTests-ul.9 Test for UTF16 with different byte orders. =============== Diff against MultilingualTests-ul.9 =============== Item was added: + TestCase subclass: #UTF16TextConverterTest + instanceVariableNames: '' + classVariableNames: '' + poolDictionaries: '' + category: 'MultilingualTests-TextConversion'! Item was added: + ----- Method: UTF16TextConverterTest>>testByteOrders (in category 'testing') ----- + testByteOrders + |converter originalText bytes decodedText | + originalText := 'test'. + converter := UTF16TextConverter new. + + "Default (ie useLittleEndian instvar nil)" + bytes := (originalText convertToWithConverter: converter). + decodedText := bytes convertFromWithConverter: converter. + + self assert: originalText equals: decodedText. + + "Little-endian" + converter useLittleEndian: true. + + bytes := (originalText convertToWithConverter: converter). + decodedText := bytes convertFromWithConverter: converter. + + self assert: originalText equals: decodedText. + + "Big-endian" + converter useLittleEndian: false. + + bytes := (originalText convertToWithConverter: converter). + decodedText := bytes convertFromWithConverter: converter. + + self assert: originalText equals: decodedText. + + !

1 0

[ANN] Discount tickets to Irish Software Show in Dublin
by Julian Fitzell 07 Jun '10

07 Jun '10

Hi everyone, I'm speaking about Seaside and web development this week at the Irish Software Show (epicenter) in Dublin. The organizers have offered each of the speakers 10 discount tickets (€50/day) to pass along to people who are interested in attending. It looks like there will be some interesting talks there on a variety of subjects including web development and cloud computing, so if you're in Dublin (or in need of a change of scenery) and would like to attend, you can check out the details here: http://epicenter.ie/2010_Julian_Fitzell_Page Julian

1 0

LikeNotepad
by Javier Diaz-Reinoso 07 Jun '10

07 Jun '10

This is a simple change set for using a workspace more like a notepad: - remove append of 'Workspace from ' in FileList>>viewContentsInWorkspace - only add '.text' in TextEditor>>saveContentsInFile when the suggestedName do not have '.text'. otherwise if you change the file and then save it, you need to cut the extra 'Workspace from ' or '.text'. What is not changed is the name of the original window, so if you start with a new workspace, then save the file, the title of the window remains as 'Workspace'.

1 0

Re: [Pharo-project] SUnit Time out
by Chris Muller 06 Jun '10

06 Jun '10

(Copying squeak-dev too). I'm not sold on the whole test timeout thing. When I run tests, I want to know the answer to the question, "is the software working?" Putting a timeout on tests trades a slower, but definitive, "yes" or "no" for a supposedly-faster "maybe". But is getting a "maybe" back really faster? I've just incurred the cost of running a test suite, but left without my answer. I get a "maybe", what am I supposed to do next? Find a faster machine? Hack into the code to fiddle with a timeout pragma? That's not faster.. But, the reason given for the change was not for running tests interactively (the 99% case), rather, all tests form the beginning of time are now saddled with a timeout for the 1% case: "The purpose of the timeout is to catch issues like infinite loops, unexpected user input etc. in automated test environments." If tests are supposed to be quick (and deterministic) anyway, wouldn't an infinite loop or user-input be caught the first time the test was run (interactively)? Seriously, when you make software changes, we run the tests interactively first, and then the purpose of night-time automated test environment is to catch regressions on the merged code.. In that case, the high-level test-controller which spits out the results could and should be responsible for handling "unexpected user input" and/or putting in a timeout, not each and every last test method.. IMO, we want short tests, so let's just write them to be short. If they're too long, then the encouragement to shorten them comes from our own impatience of running them interactively. Running them in batch at night requires no patience, because we're sleeping, and besides, the batch processor should take responsibility for handling those rare scenarios at a higher-level.. Regards, Chris On Sat, May 29, 2010 at 2:53 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Hi guys > > in Squeak andreas introduced the idea of test time out > Do you think that this is interesting? > > Stef > > SUnit > ----- > All test cases now have an associated timeout after which the test is considered failed. The purpose of the timeout is to catch issues like infinite loops, unexpected user input etc. in automated test environments. Timeouts can be set on an individual test basis using the <timeout: seconds> tag or for an entire test case by implementing the #defaultTimeout method. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

6 6

The Inbox: SUnit-dtl.79.mcz
by commits＠source.squeak.org 06 Jun '10

06 Jun '10

A new version of SUnit was added to project The Inbox: http://source.squeak.org/inbox/SUnit-dtl.79.mcz ==================== Summary ==================== Name: SUnit-dtl.79 Author: dtl Time: 6 June 2010, 3:35:25.442 pm UUID: e6568675-8893-4f0b-865f-be100c9c5c38 Ancestors: SUnit-ar.78 Provide TestCase>>timeout: as a mechanism for setting the timeout in images that do not support method annotations. For example, BitBltSimulationTest in package VMMaker requires a longer timeout value, but cannot use a <timeout:10> method annotation because it must be loadable in e.g. Squeak 3.8. The workaround for BilBltSimulationTest would be: BitBltSimulationTest>>setUp (self respondsTo: #timeout: ) ifTrue: [self perform: #timeout: with: 10] =============== Diff against SUnit-ar.78 =============== Item was added: + ----- Method: TestCase>>timeoutForSetUp (in category 'accessing') ----- + timeoutForSetUp + "Answer the timeout to use for setUp" + + | method | + method := self class lookupSelector: testSelector asSymbol. + (method pragmaAt: #timeout:) ifNotNil:[:tag| ^tag arguments first]. + ^self defaultTimeout! Item was changed: ----- Method: TestCase>>runCase (in category 'running') ----- runCase "Run this TestCase. Time out if the test takes too long." + [self timeout: [self setUp] + after: self timeoutForSetUp. + self timeout: [self performTest] + after: self timeoutForTest] + ensure: [self tearDown]! - [self timeout:[ - self setUp. - self performTest - ] after: self timeoutForTest] ensure:[self tearDown].! Item was added: + ----- Method: TestCase>>timeout: (in category 'accessing') ----- + timeout: seconds + "The timeout for a test should normally be set with a method annotation. + However, for tests that are expected to run in images that do not support + method annotations, the value may be set by setting the value from the + #setUp method (i.e. prior to running the test method)." + + timeout := seconds! Item was changed: Object subclass: #TestCase + instanceVariableNames: 'testSelector timeout' - instanceVariableNames: 'testSelector' classVariableNames: '' poolDictionaries: '' category: 'SUnit-Kernel'! TestCase class instanceVariableNames: 'history'! !TestCase commentStamp: '<historical>' prior: 0! A TestCase is a Command representing the future running of a test case. Create one with the class method #selector: aSymbol, passing the name of the method to be run when the test case runs. When you discover a new fixture, subclass TestCase, declare instance variables for the objects in the fixture, override #setUp to initialize the variables, and possibly override# tearDown to deallocate any external resources allocated in #setUp. When you are writing a test case method, send #assert: aBoolean when you want to check for an expected value. For example, you might say "self assert: socket isOpen" to test whether or not a socket is open at a point in a test.! TestCase class instanceVariableNames: 'history'! Item was changed: ----- Method: TestCase>>timeoutForTest (in category 'accessing') ----- timeoutForTest "Answer the timeout to use for this test" | method | method := self class lookupSelector: testSelector asSymbol. (method pragmaAt: #timeout:) ifNotNil:[:tag| ^tag arguments first]. + ^timeout ifNil: [self defaultTimeout]! - ^self defaultTimeout!

1 0

Jump to page: