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

Re: [Pharo-project] Issue 3394 in pharo: Adopt disappeared from Monticello Browser

by pharo＠googlecode.com

Updates: Owner: renggli Comment #2 on issue 3394 by renggli: Adopt disappeared from Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3394 (No comment was entered for this change.)

Dec. 9, 2010

[Pharo-project] need help to fix the test: testEvaluationOfSelfSend

by stephane ducasse

testEvaluationOfSelfSend "Tests the evaluation of an inherited method that uses super send and self send" | result editor | editor := self method asText asMorph editor. result := Compiler new evaluate: (self method copyFrom: 6 to: self method size) in: self model doItContext to: self model doItReceiver notifying: editor ifFail: [FakeClassPool adopt: nil. ^ #failedDoit] logged: true. self assert: result = (6250 / 3) Hi guys this test loses me. Can somebody have a look? I probably misses something obvious. Stef

Dec. 9, 2010

Re: [Pharo-project] Issue 3395 in pharo: Capitalization of Author

by pharo＠googlecode.com

Updates: Status: Fixed Owner: renggli Comment #1 on issue 3395 by renggli: Capitalization of Author http://code.google.com/p/pharo/issues/detail?id=3395 Name: System-Support-LukasRenggli.418 Author: lr Time: 9 December 2010, 5:37:10 pm UUID: 762cf0e3-e188-44f3-b675-0e22ced6f3a5 Ancestors: System-Support-StephaneDucasse.417 - do not enforce camel case on author name: - some people have lowercase words in their name (X van Y) - some projects have othe conventions

Dec. 9, 2010

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

by Noury Bouraqadi

Hi Sean, For testing you can have two approaches: -You need a mock object, and then you use a Mock library -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. It supports the creation and the deletion of classes. To ensure keeping the system clean. Noury On 9 dÃ©c. 2010, at 17:00, Sean P. DeNigris wrote: > > I was playing with creating temporary classes for testing in a separate > SystemDictionary, so I don't have to worry about removing them. But I'm a > little beyond the boundary of my knowledge (although I stepped through it in > the debugger and it seemed pretty straight forward). Are there any hidden > side-effects/implications of the following? Specifically, after the > SystemDictionary is garbage collected, is the system exactly the same as it > was before the code was run? It seems like a better approach than creating > them in the global namespace and cleaning up. > > testingEnvironment := SystemDictionary withOrganizer: SystemOrganizer new. > > ClassBuilder new > name: #AClassForTesting > inEnvironment: testingEnvironment > subclassOf: Object > type: Object typeOfClass > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'TemporaryTesting'. > > newClass := (testingEnvironment at: #AClassForTesting). > newClass > compile: 'greeting > ^ ''hello there''' > classified: 'greeting'. > > newClass new greeting. "Returns 'hello there'" > > 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

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

by pharo＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-ReportDefect Milestone-1.2 Importance-High New issue 3396 by renggli: Change Notification in Monticello Browser is broken http://code.google.com/p/pharo/issues/detail?id=3396 Packages are not marked as dirty anymore

Dec. 9, 2010

Re: [Pharo-project] Issue 3394 in pharo: Adopt disappeared from Monticello Browser

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3394 by renggli: Adopt disappeared from Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3394 Sorry, I was confused. The adopt button is still there. The change in the inbox fixes other issues with the buttons and menus: Name: MonticelloGUI-LukasRenggli.83 Author: Lr Time: 9 December 2010, 5:27:10 pm UUID: 5ba0e157-bf35-4b90-b273-4f65e6fafb4e Ancestors: MonticelloGUI-LukasRenggli.82 - fixed buttons and rearranged menu in Repository Browser - fixed some accidental changes on the default window size

Dec. 9, 2010

Re: [Pharo-project] [squeak-dev] Cog+NativeBoost @ Mac OS

by Michael Haupt

Hi Igor, here are some details. On 9 December 2010 16:29, Michael Haupt <mhaupt(a)gmail.com> wrote: > I installed the examples (which appear to be working) and tests as > well, but the tests crash the VM. I have not yet tried to nail the > problem down; is this expected behaviour on the Mac? most tests are green, but there are some issues: 1. NBUnixHeapManagerTests - 2 errors ("unable to map to virtual memory") 2. NBCallbackTests - assertion failure in NBInterpreterProxy >> #callInterpreter I installed NB in a clean up-to-date Squeak trunk image and use the Cog/NB VM from the NB Google code page. Best, Michael

Dec. 9, 2010

[Pharo-project] Creating temporary classes for testing

by Sean P. DeNigris

I was playing with creating temporary classes for testing in a separate SystemDictionary, so I don't have to worry about removing them. But I'm a little beyond the boundary of my knowledge (although I stepped through it in the debugger and it seemed pretty straight forward). Are there any hidden side-effects/implications of the following? Specifically, after the SystemDictionary is garbage collected, is the system exactly the same as it was before the code was run? It seems like a better approach than creating them in the global namespace and cleaning up. testingEnvironment := SystemDictionary withOrganizer: SystemOrganizer new. ClassBuilder new name: #AClassForTesting inEnvironment: testingEnvironment subclassOf: Object type: Object typeOfClass instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'TemporaryTesting'. newClass := (testingEnvironment at: #AClassForTesting). newClass compile: 'greeting ^ ''hello there''' classified: 'greeting'. newClass new greeting. "Returns 'hello there'" 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

[Pharo-project] Issue 3395 in pharo: Capitalization of Author

by pharo＠googlecode.com

Status: Accepted Owner: ---- Labels: Difficulty-Easy Type-ToDo Milestone-1.2 New issue 3395 by renggli: Capitalization of Author http://code.google.com/p/pharo/issues/detail?id=3395 The author initials are automatically capitalized, this is extremely annoying! Not everybody is following the PharoCore people conventions.

Dec. 9, 2010

[Pharo-project] Issue 3394 in pharo: Adopt disappeared from Monticello Browser

by pharo＠googlecode.com

Status: Accepted Owner: ---- Labels: Milestone-1.2 Difficulty-Easy New issue 3394 by renggli: Adopt disappeared from Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3394 The adopt button disappeared, which is a sensible change. The adopt functionality should still be available from the menu, because it is a common operation when integrating.

Dec. 9, 2010