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

[Pharo-project] Issue 3860 in pharo: Overzealous arithmetic collection removal
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Status: Accepted Owner: ryd...(a)gmail.com Labels: Milestone-1.3 New issue 3860 by ryd...(a)gmail.com: Overzealous arithmetic collection removal http://code.google.com/p/pharo/issues/detail?id=3860 Separated to http://www.squeaksource.com/CollectionArithmetic. FloatArray and WordArray methods should be moved back into the image, as these specifically are numerical collections, not for general storage. It makes very little sense to remove the operations, but keep the primitive methods they use... Also be careful dot: change from Issue 3701 is not reverted when merging.

1 0

[Pharo-project] Issue 3858 in pharo: On windows, Error when dropping an image in the vm
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Status: Accepted Owner: cy.delau...(a)gmail.com New issue 3858 by cy.delau...(a)gmail.com: On windows, Error when dropping an image in the vm http://code.google.com/p/pharo/issues/detail?id=3858 On windows, when you want to open an image by dropping it on the vm icon, The image is opened with an Error

1 5

[Pharo-project] Issue 3667 in pharo: ThreadSafeTranscript does not understand crtab and crtab:
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Status: New Owner: ---- New issue 3667 by mathias.kegelmann: ThreadSafeTranscript does not understand crtab and crtab: http://code.google.com/p/pharo/issues/detail?id=3667 Several methods send crtab and crtab: so it would be useful if ThreadSafeTranscript implemented them.

1 3

[Pharo-project] Issue 3701 in pharo: FloatArray>>dot: is defined in plugin but not at the image level
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Status: FixedWaitingToBePharoed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 Type-Squeak Difficulty-Easy New issue 3701 by stephane...(a)gmail.com: FloatArray>>dot: is defined in plugin but not at the image level http://code.google.com/p/pharo/issues/detail?id=3701 Name: Collections-ul.423 Author: ul Time: 7 February 2011, 8:55:57.134 pm UUID: e18716fc-a36b-874c-8946-5c21b447a96f Ancestors: Collections-ul.422 - use the primitive for FloatArray >> #dot: (~50x faster). =============== Diff against Collections-ul.422 =============== Item was changed: ----- Method: FloatArray>>dot: (in category 'arithmetic') ----- dot: aFloatVector "Primitive. Return the dot product of the receiver and the argument. Fail if the argument is not of the same size as the receiver." + | result | + <primitive: 'primitiveDotProduct' module: 'FloatArrayPlugin'> - "<primitive:'primitiveFloatArrayDotProduct'>" self size = aFloatVector size ifFalse:[^self error:'Must be equal size']. result := 0.0. 1 to: self size do:[:i| result := result + ((self at: i) * (aFloatVector at: i)). ]. ^result!

1 2

[Pharo-project] Issue 3638 in pharo: look for sender of etoyCleaningLeftToDo
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Status: Accepted Owner: stephane...(a)gmail.com New issue 3638 by stephane...(a)gmail.com: look for sender of etoyCleaningLeftToDo http://code.google.com/p/pharo/issues/detail?id=3638 there are still code to clean

1 3

[Pharo-project] [update 1.3] #13107
by Marcus Denker March 24, 2011

March 24, 2011

13107 ----- Issue 3768: Deprecate String >> get/putInteger32: Issue 1765: JPEGReadWriter>>#decompressionTest should be made into a Sunit Test Issue 2240: CondenseChange Trait Tests Issue 2786: Mixed concerns on Object>>saveOnFile Issue 3638: look for sender of etoyCleaningLeftToDo Issue 3701: FloatArray>>dot: is defined in plugin but not at the image level Issue 3667: ThreadSafeTranscript does not understand crtab and crtab: -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Issue 2786 in pharo: Mixed concerns on Object>>saveOnFile
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #2 on issue 2786 by marcus.d...(a)gmail.com: Mixed concerns on Object>>saveOnFile http://code.google.com/p/pharo/issues/detail?id=2786 saveOnFile is categorized *morphic, but Morph reimplements it. No senders and not a good idea anyway. Attached changeset removes it Attachments: KillSaveOnFile.1.cs 133 bytes

1 1

Re: [Pharo-project] Issue 2240 in pharo: CondenseChange Trait Tests
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Updates: Status: FixProposed Comment #4 on issue 2240 by marcus.d...(a)gmail.com: CondenseChange Trait Tests http://code.google.com/p/pharo/issues/detail?id=2240 code with the test attached. Test is green. The changeset adds some methods to MethodReference that where missed when removing LocatedMethod. Attachments: TraitsFileOutTest.2.cs 2.7 KB

1 1

Re: [Pharo-project] Issue 1765 in pharo: JPEGReadWriter>>#decompressionTest should be made into a Sunit Test
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Comment #4 on issue 1765 by jannik.l...(a)gmail.com: JPEGReadWriter>>#decompressionTest should be made into a Sunit Test http://code.google.com/p/pharo/issues/detail?id=1765 "JPEGReadWriter new decompressionTest" raise an error. Are you sure this method works fine?

1 3

[Pharo-project] Issue 3768 in pharo: Deprecate String >> get/putInteger32:
by pharo＠googlecode.com March 24, 2011

March 24, 2011

Status: Accepted Owner: ryd...(a)gmail.com Labels: Milestone-1.3 New issue 3768 by ryd...(a)gmail.com: Deprecate String >> get/putInteger32: http://code.google.com/p/pharo/issues/detail?id=3768 String >> #getInteger32: & String >> #putInteger32:at: Previously used by Nebraska to send SmallIntegers in Strings through sockets. If there are any senders in packages we expect to load, they should find better/clearer ways to do what these methods can currently be used for.

1 2