November 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Comment Syntax
by Sean P. DeNigris Nov. 3, 2011

Nov. 3, 2011

Would it be difficult/valuable to create an alternate comment syntax? I often find myself wanting to comment a large block itself containing comments. It would be nice to have something like C++'s /* */. I feel like this may have been brought up before, but couldn't find it searching the lists. Sean -- View this message in context: http://forum.world.st/Comment-Syntax-tp3961451p3961451.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

10 14

[Pharo-project] FS Quirks
by Sean P. DeNigris Nov. 3, 2011

Nov. 3, 2011

I noticed a few things about FS, but I don't understand it well enough yet to know if they are bugs: * there are #basicXxx methods scattered around with no corresponding #xxx method. It seems like these should be renamed to #xxx * FSFileSystem has #open:writable which does not call #basicOpen:writable, which exists * FSReference>>rename:as:, but FSFilePluginPrims>>rename:to: (to: sounds better to me) -- View this message in context: http://forum.world.st/FS-Quirks-tp3986296p3986296.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] Small tool to edit bloc code
by Hilaire Fernandes Nov. 3, 2011

Nov. 3, 2011

>From DrGeo I would like the user to edit Smalltalk code in the form of block of code. The user interface I need is maninly to let the user write and compile code. When compiled, DrGeo should get a notification to fetch the code for internal use. What is the best candidate to do that ? Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

3 4

[Pharo-project] FSReference
by Sean P. DeNigris Nov. 3, 2011

Nov. 3, 2011

I'm /really/ enjoying FS (I couldn't wait so I loaded it into 1.3-rc; all working so far). I keep finding myself writing things like: FSReference>>doSomething "double dispatch extension method" self isDirectory ifTrue: [ ... ] ifFalse: [ ... ]. I feel dirty every time, but FS doesn't make this piece of a reference's identity explicit. Would it be valuable to have FSFileReference and FSDirectoryReference subclasses? It would certainly make my code cleaner as I could then double dispatch without conditionals. Thanks. Sean -- View this message in context: http://forum.world.st/FSReference-tp3985640p3985640.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 3

[Pharo-project] SortDescriptors
by HwaJong Oh Nov. 3, 2011

Nov. 3, 2011

I've ported NSSortDescriptor to Pharo. It works well with SortedCollection and has more features. Gofer new squeaksource: 'DaliotsPlayground'; package: 'ConfigurationOfDaliotsPlayground'; load. (Smalltalk at: #ConfigurationOfDaliotsPlayground) project lastVersion load: 'SortDescriptors'. Take a look the class comment and unittests. HwaJong Oh -- View this message in context: http://forum.world.st/SortDescriptors-tp3985696p3985696.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] adding author to compiledMethod and authors to class.
by StÃ©phane Ducasse Nov. 3, 2011

Nov. 3, 2011

http://code.google.com/p/pharo/issues/detail?id=4971

1 0

[Pharo-project] Issue tracker states
by Marcus Denker Nov. 3, 2011

Nov. 3, 2011

Hi, We started to improve the states defined in the tracker... this now has: FixToInclude = QA has verified that the fix worked, needs to be integrated FixReviewNeeded = Code is there, but a review is needed NoSourcesAvailable = fix proposed, but machine readable code missing Workneeded = Next action is defined but not yet completed NextActionNeeded = What is the next action? Accepted = Problem reproduced / Need acknowledged New = Nobody looked at this yet OnHold = We will come back later to this issue, no action possible now The issue tracker by default sorts the items to show the ones on top that have progressed the most: http://code.google.com/p/pharo/issues/list The idea is that the "FixToInclude" status should be integrated very quickly (within a day), later maybe even automatically. Marcus -- Marcus Denker -- http://marcusdenker.de

6 6

[Pharo-project] #at:ifAbsent: for Array(s) could be faster
by Igor Stasenko Nov. 3, 2011

Nov. 3, 2011

Here the original implementation, which Array inherits from SequenceableCollection: at: index ifAbsent: exceptionBlock "Answer the element at my position index. If I do not contain an element at index, answer the result of evaluating the argument, exceptionBlock." (index between: 1 and: self size) ifTrue: [^ self at: index]. ^ exceptionBlock value the thing is, that #at: primivite also doing a range checking and fails if index is invalid, so if index is valid, as result we performing a range checking twice instead of just once. Here the simple implementation how to make things faster: fat: index "Primitive. Assumes receiver is indexable. Answer the value of an indexable element in the receiver. Fail if the argument index is not an Integer or is out of bounds. Essential. See Object documentation whatIsAPrimitive. Read the class comment for a discussion about that the fact that the index can be a float." <primitive: 60> ^ #plopp fat: index ifAbsent: aBlock | x | x := (self fat: index). x == #plopp ifTrue: [ ^ aBlock value ]. ^ x And speedup is almost 2 times: [ 1000000 timesRepeat: [ #(1 2 4 5 56 67 67) at: 1 ifAbsent: nil ] ] timeToRun 39 [ 1000000 timesRepeat: [ #(1 2 4 5 56 67 67) at: 1 ifAbsent: nil ] ] timeToRun 20 Even when index is out of range, it is still much faster: [ 1000000 timesRepeat: [ #(1 2 4 5 56 67 67) at: 100 ifAbsent: nil ] ] timeToRun 35 [ 1000000 timesRepeat: [ #(1 2 4 5 56 67 67) fat: 100 ifAbsent: nil ] ] timeToRun 24 The problem, of course, that trick with #plopp is a dirty hack. Because if array include an #plopp object as element, it will report as it absent, instead of answering it. There is no way to ensure that any arbitrary object are never included as element in array, so this is no-go for generic replacement. But in controlled environment, when you know that none of arrays which you using with #fat:ifAbsent: will ever include #plopp (or pick your own unique object) it may be a good alternative. -- Best regards, Igor Stasenko.

5 4

Re: [Pharo-project] #at:ifAbsent: for Array(s) could be faster
by Dave Mason Nov. 2, 2011

Nov. 2, 2011

On Nov 2, 2011, at 14:21, Igor Stasenko wrote: > The problem, of course, that trick with #plopp is a dirty hack. > Because if array include an #plopp object as element, it will report > as it absent, instead of answering it. > There is no way to ensure that any arbitrary object are never included > as element in array, so this is no-go for generic replacement. > But in controlled environment, when you know that none of arrays which > you using with #fat:ifAbsent: will ever include #plopp (or pick your > own unique object) it may be a good alternative. If Array class initialize said: NonUserValue := Object new then #plopp can be replaced with NonUserValue and nobody can get at it unless they really intend to (e.g. by making Array be in their classPool). ../Dave

1 0

[Pharo-project] Small tool to edit bloc code
by Hilaire Fernandes Nov. 2, 2011

Nov. 2, 2011

>From DrGeo I would like the user to edit Smalltalk code in the form of block of code. The user interface I need is maninly to let the user write and compile code. When compiled, DrGeo should get a notification to fetch the code for internal use. What is the best candidate to do that ? Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

2 1