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

[Pharo-project] Issue 3463 in pharo: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses

by pharo＠googlecode.com

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

Dec. 20, 2010

[Pharo-project] Issue 3462 in pharo: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses

by pharo＠googlecode.com

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

Dec. 20, 2010

Re: [Pharo-project] Are we tagging 1.2 dev issues?

by Marcus Denker

On Dec 20, 2010, at 8:38 AM, Marcus Denker wrote: > > On Dec 20, 2010, at 4:27 AM, Guillermo Polito wrote: > >> I found only 5 in the issue tracker, hehe. Maybe those are the only reported by now, maybe not. >> I added tracker entries for all failing tests that are not yet entries for 1.2Core: http://code.google.com/p/pharo/issues/list?cursor=3462&q=milestone%3D1.2-De… Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 20, 2010

[Pharo-project] Issue 3461 in pharo: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses

by pharo＠googlecode.com

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

Dec. 20, 2010

[Pharo-project] Issue 3460 in pharo: [Failing Test] ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2-DevImage New issue 3460 by marcus.denker: [Failing Test] ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812 http://code.google.com/p/pharo/issues/detail?id=3460 ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

Dec. 20, 2010

Re: [Pharo-project] Issue 3454 in pharo: DNU when looking for implementors in OB on 1.2dev

by pharo＠googlecode.com

Comment #2 on issue 3454 by marcus.denker: DNU when looking for implementors in OB on 1.2dev http://code.google.com/p/pharo/issues/detail?id=3454 The following failing tests look related to that: >>> OB.Tests.Morphic.OBKeyBindingsTest.testBrowseIt 0.332 10 >>> OB.Tests.Morphic.OBKeyBindingsTest.testImplementorsOfIt 0.384 10 >>> OB.Tests.Morphic.OBKeyBindingsTest.testReferencesToIt 0.248 10 >>> OB.Tests.Morphic.OBKeyBindingsTest.testSendersOfIt 0.265 10

Dec. 20, 2010

Re: [Pharo-project] Printing hexadecimal values of a string

by Geoffroy Couprie

2010/12/20 Levente Uzonyi <leves(a)elte.hu>: > On Mon, 20 Dec 2010, Geoffroy Couprie wrote: > >> Hello, >> >> 2010/12/20 Levente Uzonyi <leves(a)elte.hu>: >>> >>> On Mon, 20 Dec 2010, StÃ©phane Ducasse wrote: >>> >>>> >>>> >>>> On Dec 19, 2010, at 9:55 PM, Geoffroy Couprie wrote: >>>> >>>>> Hello all, >>>>> >>>>> I get a strange behaviour while trying to print hexadecimal values of a >>>>> string. >>>>> >>>>> Context: I get a SHA1 hash from a binary stream, store it into a >>>>> string, and I want to display that string (using asHex). >>>>> >>>>> Problem: for values inferior to 16, the leading zero is ignored. (15 >>>>> -> 'F' instead of '0F'). >>>> >>>> indeed printStringHex prints F instead of 0F >>>> 15 printStringHex >>>> Â Â Â Â 'F' >>>> 15 hex >>>> Â Â Â Â '16rF' >>>> >>>> Geoffroy could you add a variant that produces the correct behavior with >>>> some tests? >>> >>> No need to do that. As Sven pointed out, he can simply use ByteArray >> >>> #hex. Since his stream is already binary, he can also avoid converting >>> his >>> data to a string. >>> >> >> More context: I am using a ZLibReadStream and its upTo: method, which >> gives me a ByteString, not a ByteArray. I guess I could convert it to >> a ByteArray. >> >> But I still think there's a bug here: printing the hex value of a >> Character should add the leading zero, because they're represented by >> a full byte. >> >> So, I propose this change: >> >> Character>>hex >> Â ^value printStringBase: 16 nDigits: 2 >> >> > > What about this? > > (Character value: 12345) hex > Huh, I forgot multibyte characters... Then would this be sufficient? Character>>hex value >255 ifTrue: [^value hex] ifFalse: [^value printStringBase: 16 nDigits: 2]

Dec. 20, 2010

Re: [Pharo-project] Printing hexadecimal values of a string

by Levente Uzonyi

On Mon, 20 Dec 2010, Geoffroy Couprie wrote: > Hello, > > 2010/12/20 Levente Uzonyi <leves(a)elte.hu>: >> On Mon, 20 Dec 2010, StÃ©phane Ducasse wrote: >> >>> >>> >>> On Dec 19, 2010, at 9:55 PM, Geoffroy Couprie wrote: >>> >>>> Hello all, >>>> >>>> I get a strange behaviour while trying to print hexadecimal values of a >>>> string. >>>> >>>> Context: I get a SHA1 hash from a binary stream, store it into a >>>> string, and I want to display that string (using asHex). >>>> >>>> Problem: for values inferior to 16, the leading zero is ignored. (15 >>>> -> 'F' instead of '0F'). >>> >>> indeed printStringHex prints F instead of 0F >>> 15 printStringHex >>> Â Â Â Â 'F' >>> 15 hex >>> Â Â Â Â '16rF' >>> >>> Geoffroy could you add a variant that produces the correct behavior with >>> some tests? >> >> No need to do that. As Sven pointed out, he can simply use ByteArray >> >> #hex. Since his stream is already binary, he can also avoid converting his >> data to a string. >> > > More context: I am using a ZLibReadStream and its upTo: method, which > gives me a ByteString, not a ByteArray. I guess I could convert it to > a ByteArray. > > But I still think there's a bug here: printing the hex value of a > Character should add the leading zero, because they're represented by > a full byte. > > So, I propose this change: > > Character>>hex > ^value printStringBase: 16 nDigits: 2 > > What about this? (Character value: 12345) hex Levente

Dec. 20, 2010

Re: [Pharo-project] Issue 3459 in pharo: includesSubstring: aString caseSensitive: caseSensitive / includesSubString:

by pharo＠googlecode.com

Comment #1 on issue 3459 by Benjamin.VanRyseghem.Pharo: includesSubstring: aString caseSensitive: caseSensitive / includesSubString: http://code.google.com/p/pharo/issues/detail?id=3459 I'm talking about the selector of those methods

Dec. 20, 2010

[Pharo-project] Issue 3459 in pharo: includesSubstring: aString caseSensitive: caseSensitive / includesSubString:

by pharo＠googlecode.com

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3459 by Benjamin.VanRyseghem.Pharo: includesSubstring: aString caseSensitive: caseSensitive / includesSubString: http://code.google.com/p/pharo/issues/detail?id=3459 Maybe one of this two methods should be changed in order to start as the other one (includesSubstring: aString caseSensitive: caseSensitive have only 14 senders ^^)

Dec. 20, 2010