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

[Pharo-project] Issue 3493 in pharo: Remove definitely MessagesNames and MethodFinder
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Status: Accepted Owner: marianopeck Labels: Milestone-1.3 New issue 3493 by marianopeck: Remove definitely MessagesNames and MethodFinder http://code.google.com/p/pharo/issues/detail?id=3493 In Pharo 1.2, we remove those guys from the menu. Now in 1.3 we should really remove them (remove its code).

1 1

[Pharo-project] Issue 3461 in pharo: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2-DevImage New issue 3461 by marcus.denker: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses http://code.google.com/p/pharo/issues/detail?id=3461 Tests.Release.ReleaseTest.testObsoleteClasses

1 3

[Pharo-project] Issue 3440 in pharo: Cycle in Monticello removed
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: alexandre.bergel CC: stephane.ducasse Labels: Difficulty-Easy New issue 3440 by alexandre.bergel: Cycle in Monticello removed http://code.google.com/p/pharo/issues/detail?id=3440 A cycle is due to a dependency of Monticello-Chunk Format to Monticello-Storing. Monticello-FelipeValverde.472 in the inBox fixes this. DSM was used for this. Result of the CC68S lecture

1 4

[Pharo-project] Issue 3361 in pharo: CompiledMethod's copy
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: gbarbuto New issue 3361 by gbarbuto: CompiledMethod's copy http://code.google.com/p/pharo/issues/detail?id=3361 Pharo image: core Pharo core version: Pharo1.2a Latest update: #12264 Virtual machine used: <any Steps to reproduce: 1. Try to completely copy a CompiledMethod and the copy still have references to the original CompiledMethod.

1 4

[Pharo-project] Issue 3491 in pharo: Preferences are still referenced in Pharo-dev 1.2
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: Torsten....(a)astares.de New issue 3491 by Torsten....(a)astares.de: Preferences are still referenced in Pharo-dev 1.2 http://code.google.com/p/pharo/issues/detail?id=3491 see Pen>>arrowHead and EnvelopeEditorMorph>>wantsRoundedCorners also in Soundsystem (see http://code.google.com/p/pharo/issues/detail?id=3489) and the metacello config (see http://code.google.com/p/pharo/issues/detail?id=3490)

1 3

[Pharo-project] Issue 3420 in pharo: ReleaseTest>>#testUndeclared is failing
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3420 by marcus.denker: ReleaseTest>>#testUndeclared is failing http://code.google.com/p/pharo/issues/detail?id=3420 ReleaseTest>>#testUndeclared is failing I think the hudson build code adds references to RB

1 7

[Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3419 by marcus.denker: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing http://code.google.com/p/pharo/issues/detail?id=3419 TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

1 7

Re: [Pharo-project] Issue 3464 in pharo: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Updates: Summary: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory Comment #1 on issue 3464 by marcus.denker: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3464 (No comment was entered for this change.)

1 1

[Pharo-project] Issue 3458 in pharo: bug in the class MultiByteFileStream when Pharo running under Windows
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: New Owner: ---- New issue 3458 by mmk.bbt: bug in the class MultiByteFileStream when Pharo running under Windows http://code.google.com/p/pharo/issues/detail?id=3458 PharoCore-1.2beta-12272, Windows Steps to reproduce: (MultiByteFileStream new) wantsLineEndConversion: true; open: 'c:\temp\1.txt' forWrite: true; cr; close. File c:\temp\1.txt contains 3 characters (cr lf lf) instead of two (cr lf). This is due to the fact that the method MultiByteFileStream>> nextPut: There is a double conversion of Cr to CrLf. I think this can be corrected as follows: " MultiByteFileStream>> nextPut: aCharacter aCharacter isInteger ifTrue: [^ super nextPut: aCharacter]. (wantsLineEndConversion == true and: [lineEndConvention notNil]) "# doConversion is inlined here" ifTrue: [ aCharacter = Cr ifTrue: [converter nextPutAll: (LineEndStrings at: # cr) toStream: self] ifFalse: [converter nextPut: aCharacter toStream: self]. ^ aCharacter]. ^ Self converter nextPut: aCharacter toStream: self " Sincerely, Maxim Paste or attach stack trace if applicable (look at the file PharoDebug.log located in the same directory as your image):

1 7

[Pharo-project] Issue 3413 in pharo: WeakFinalizersTest.testNewFinalizationSupported fails on Hudson builder
by pharo＠googlecode.com Jan. 20, 2011

Jan. 20, 2011

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3413 by marcus.denker: WeakFinalizersTest.testNewFinalizationSupported fails on Hudson builder http://code.google.com/p/pharo/issues/detail?id=3413 WeakFinalizersTest.testNewFinalizationSupported fails on Hudson builder Do we need a newer VM?

1 3