- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3386 in pharo: DosFileDirectory>> checkName: aFileName fixErrors: fixing
by pharo＠googlecode.com Dec. 11, 2010

Dec. 11, 2010

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3386 by stephane.ducasse: DosFileDirectory>> checkName: aFileName fixErrors: fixing http://code.google.com/p/pharo/issues/detail?id=3386 DosFileDirectory>> checkName: aFileName fixErrors: fixing "Check if the file name contains any invalid characters" | fName badChars hasBadChars | fName := super checkName: aFileName fixErrors: fixing. badChars := (#( $: $< $> $| $/ $\ $? $* $"), ((0 to: 31) collect: [:n | n asCharacter])) asSet. hasBadChars := fName includesAnyOf: badChars. (hasBadChars and:[fixing not]) ifTrue:[^self error:'Invalid file name']. hasBadChars ifFalse:[^ fName]. ^ fName collect: [:char | (badChars includes: char) ifTrue:[$#] ifFalse:[char]]

1 2

[Pharo-project] Issue 3397 in pharo: Behaviour>> #adoptInstance:
by pharo＠googlecode.com Dec. 11, 2010

Dec. 11, 2010

Status: Started Owner: rydier Labels: Milestone-1.2 New issue 3397 by rydier: Behaviour>> #adoptInstance: http://code.google.com/p/pharo/issues/detail?id=3397 This is a method originally found in VisualWorks, and offers a nicer interface to use than changeClassToThatOf: for switching the class of an instance. Cog has added primitive support for this, the fallback code uses the equivalent primitiveChangeClassTo: which works in non-Cog vms. (But takes an instance rather than a class, usually not very convenient when you want to use it)

1 3

[Pharo-project] Issue 3400 in pharo: doubled '.' at end of line in RxParserTest>>#test and #testTranlsatingMatchesUsing not portable
by pharo＠googlecode.com Dec. 11, 2010

Dec. 11, 2010

Status: Started Owner: da...@teleport.com Labels: Milestone-1.2 New issue 3400 by da...@teleport.com: doubled '.' at end of line in RxParserTest>>#test and #testTranlsatingMatchesUsing not portable http://code.google.com/p/pharo/issues/detail?id=3400 attempting to load Regex-Tests-Core-StephaneDucasse.2 into GemStone results in compile errors. should be able to remove the offending periods with little impact ... I'll check in an update package shortly

1 4

[Pharo-project] ctlr-C in code.google.... gets on my nerves
by StÃ©phane Ducasse Dec. 11, 2010

Dec. 11, 2010

Hi apparently the ctrl-C behavior has changed on the bug tracker. Does anybody know how to control that it just copy and paste and do not create a new issue? Stef

1 0

[Pharo-project] Linux VM with IA32ABI plugin (Alien)
by Luc Fabresse Dec. 10, 2010

Dec. 10, 2010

Hi all, I know that someone already manage to compile linux (squeak or cog) VM with Alien support (plugin I32ABI). Could someone, send me an already compiled VM? ;-) BTW, why the compiled linux VM available for download does not include this plugin? Thanks, #Luc

2 3

[Pharo-project] Where does Regex-Core and friends live
by Dale Henrichs Dec. 10, 2010

Dec. 10, 2010

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

4 12

Re: [Pharo-project] Issue 3254 in pharo: [Repackage] "Regular expressions" should be well structured
by pharo＠googlecode.com Dec. 10, 2010

Dec. 10, 2010

Updates: Cc: marcus.denker Comment #10 on issue 3254 by Torsten....@astares.de: [Repackage] "Regular expressions" should be well structured http://code.google.com/p/pharo/issues/detail?id=3254 So stef integrated the latest version available on lukas repository. Ready for inclusion in 1.2 then?

1 3

Re: [Pharo-project] Issue 3263 in pharo: Add a followingBytecode to InstructionStream
by pharo＠googlecode.com Dec. 10, 2010

Dec. 10, 2010

Comment #2 on issue 3263 by siguctua: Add a followingBytecode to InstructionStream http://code.google.com/p/pharo/issues/detail?id=3263 it would be nice to have a test, which covering this refactoring

1 0

[Pharo-project] Issue 3399 in pharo: SystemNavigation should directly use CompiledMethods instead of their wrapper where its appropriate
by pharo＠googlecode.com Dec. 10, 2010

Dec. 10, 2010

Status: Accepted Owner: siguctua Labels: Milestone-1.3 New issue 3399 by siguctua: SystemNavigation should directly use CompiledMethods instead of their wrapper where its appropriate http://code.google.com/p/pharo/issues/detail?id=3399 SystemNavigation exposing the currently running system to tools. This means that it is always operates with objects located in system in its current state, not somewhere outside. In own turn this means, that it should not use any indirections or wrapping real compiled methods with method references, but instead should pass them directly to development tools. For navigating remote systems or any other kinds of indirection, one could create a subclass of SystemNavigation, which then can expose the remote system internal using compiled method references, classes and other proxies like that. This also means that we should analyze and impose the required protocol which both CompiledMethod and MethodReference(s) should comply with. As well as Classes and MetaClasses, Packages and organization.

1 0

[Pharo-project] Creating temporary classes for testing
by Sean P. DeNigris Dec. 10, 2010

Dec. 10, 2010

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.

4 8