- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 1264 in pharo: ConnectionTimedOut when running NetNameResolver testIPv6Echo
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Updates: Status: Closed Comment #2 on issue 1264 by marcus.d...(a)gmail.com: ConnectionTimedOut when running NetNameResolver testIPv6Echo http://code.google.com/p/pharo/issues/detail?id=1264 Network code was reverted before 1.1, method does nor exist.

1 0

Re: [Pharo-project] Issue 2001 in pharo: Positionable stream hardcodes end of line delimiter
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Updates: Status: Closed Comment #1 on issue 2001 by marcus.d...(a)gmail.com: Positionable stream hardcodes end of line delimiter http://code.google.com/p/pharo/issues/detail?id=2001 this has been fixed... in 1.2: nextLine "Answer next line (may be empty) without line end delimiters, or nil if at end. Let the stream positioned after the line delimiter(s). Handle a zoo of line delimiters CR, LF, or CR-LF pair" self atEnd ifTrue: [^nil]. ^self upToAnyOf: CharacterSet crlf do: [:char | char = Character cr ifTrue: [self peekFor: Character lf]]

1 0

[Pharo-project] Issue 3529 in pharo: TextMorph>>releaseCachedState creates a paragraph which causes a "Subscript out of bounds" in an internal RunArray
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Status: Accepted Owner: hernan.m...(a)gmail.com Labels: Type-ReportDefect New issue 3529 by hernan.m...(a)gmail.com: TextMorph>>releaseCachedState creates a paragraph which causes a "Subscript out of bounds" in an internal RunArray http://code.google.com/p/pharo/issues/detail?id=3529 Pharo image: Pharo1.1rc3 Pharo core version: Latest update: #11406 Virtual machine used: Pharo 4.0.2 Steps to reproduce: 1. ScriptLoader new cleanUpForRelease. or 2. Specifically SystemNavigation default allObjectsDo: [ :each | (each respondsTo: #releaseCachedState) ifTrue: [ each releaseCachedState ] ]. Sometimes creating a new paragraph while releasing caches causes an Error (subscript is out of bounds) in the RunArray of the text attributes of the TextComposer in the MultiNewParagraph which is contained. Attached Error log. The method TextMorph>>paragraph says "Paragraph instantiation is lazy -- it will be created only when needed", then why the (undocumented) TextMorph>>releaseCachedState creates a new paragraph anyway? If creating paragraph is not needed you may apply the proposed fix. Attachments: releaseParagraphBug.log 29.9 KB TextMorph-releaseCachedState.st 234 bytes

1 1

[Pharo-project] Issue 3671 in pharo: Shout: mark ByteArray literals as ByteArrays instead of Arrays
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Status: FixedWaitingToBePharoed Owner: stephane...(a)gmail.com Labels: Type-Squeak Milestone-1.3 New issue 3671 by stephane...(a)gmail.com: Shout: mark ByteArray literals as ByteArrays instead of Arrays http://code.google.com/p/pharo/issues/detail?id=3671 Name: ShoutCore-ul.28 Author: ul Time: 28 January 2011, 1:17:21.77 am UUID: 29ed9d42-0ccc-fc49-a38d-57214f045916 Ancestors: ShoutCore-ul.27 - mark ByteArray literals as ByteArrays instead of Arrays =============== Diff against ShoutCore-ul.27 =============== Item was changed: ----- Method: SHParserST80>>parseByteArray (in category 'parse') ----- parseByteArray [currentTokenFirst == $]] whileFalse: [ currentTokenFirst isDigit ifTrue: [ "do not parse the number, can be time consuming" self scanPast: #number] ifFalse: [ self failWhen: currentTokenFirst == $. . self error]]. + self scanPast: #byteArrayEnd! - self scanPast: #arrayEnd! Item was changed: ----- Method: SHParserST80>>parseSymbol (in category 'parse') ----- parseSymbol | c | currentToken = '#' ifTrue: [ "if token is just the #, then scan whitespace and comments and then process the next character. Squeak allows space between the # and the start of the symbol e.g. # (), # a, # 'sym' " self rangeType: #symbol. self scanWhitespace]. c := self currentChar. self failWhen: (c isNil or: [c isSeparator]). c == $( ifTrue: [ self nextChar. self scanPast: #arrayStart start: currentTokenSourcePosition end: currentTokenSourcePosition + 1. ^self parseArray]. c == $' ifTrue: [^self parseSymbolString]. c == $[ ifTrue: [ self nextChar. + self scanPast: #byteArrayStart start: currentTokenSourcePosition end: currentTokenSourcePosition + 1. - self scanPast: #arrayStart start: currentTokenSourcePosition end: currentTokenSourcePosition + 1. ^self parseByteArray]. ((self isSelectorCharacter: c) or: [c == $-]) ifTrue: [^self parseSymbolSelector]. (c isLetter or: [ c == $: or: [ c == $_ and: [self allowUnderscoreSelectors] ] ]) ifTrue: [^self parseSymbolIdentifier]. ^self parseCharSymbol! Item was changed: ----- Method: SHTextStylerST80 class>>defaultStyleTable (in category 'style table') ----- defaultStyleTable "color can be a valid argument to Color class>>colorFrom: , or nil to use the editor text color. Multiple emphases can be specified using an array e.g. #(bold italic). If emphasis is not specified, #normal will be used. if pixel height is not specified , then the editor font size will be used. " ^#( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default black ) (invalid red ) (excessCode red ) (comment (green muchDarker) italic) (unfinishedComment (red muchDarker) italic) (#'$' (red muchDarker) ) (character (red muchDarker) ) (integer (red muchDarker) ) (number (red muchDarker) ) (#- (red muchDarker) ) (symbol (blue muchDarker) bold) (stringSymbol (blue muchDarker) bold) (literalArray (blue muchDarker) bold) (string (magenta muchDarker) normal) (unfinishedString red normal ) (assignment nil bold ) (ansiAssignment nil bold) (literal nil italic) (keyword (blue muchDarker) ) (binary (blue muchDarker) ) (unary (blue muchDarker) ) (incompleteKeyword (gray muchDarker) underlined) (incompleteBinary (gray muchDarker) underlined) (incompleteUnary (gray muchDarker) underlined) (undefinedKeyword red ) (undefinedBinary red ) (undefinedUnary red ) (patternKeyword nil bold) (patternBinary nil bold) (patternUnary nil bold) (#self (red muchDarker) bold) (#super (red muchDarker) bold) (#true (red muchDarker) bold) (#false (red muchDarker) bold) (#nil (red muchDarker) bold) (#thisContext (red muchDarker) bold) (#return (red muchDarker) bold) (patternArg (blue muchDarker) italic) (methodArg (blue muchDarker) italic) (blockPatternArg (blue muchDarker) italic) (blockArg (blue muchDarker) italic) (argument (blue muchDarker) italic) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 (green muchDarker) ) (rightParenthesis1 (green muchDarker) ) (leftParenthesis2 (magenta muchDarker) ) (rightParenthesis2 (magenta muchDarker) ) (leftParenthesis3 (red muchDarker) ) (rightParenthesis3 (red muchDarker) ) (leftParenthesis4 (green darker) ) (rightParenthesis4 (green darker) ) (leftParenthesis5 (orange darker) ) (rightParenthesis5 (orange darker) ) (leftParenthesis6 (magenta darker) ) (rightParenthesis6 (magenta darker) ) (leftParenthesis7 blue ) (rightParenthesis7 blue ) (blockStart black ) (blockEnd black ) (blockStart1 (green muchDarker) ) (blockEnd1 (green muchDarker) ) (blockStart2 (magenta muchDarker) ) (blockEnd2 (magenta muchDarker) ) (blockStart3 (red muchDarker) ) (blockEnd3 (red muchDarker) ) (blockStart4 (green darker) ) (blockEnd4 (green darker) ) (blockStart5 (orange darker) ) (blockEnd5 (orange darker) ) (blockStart6 (magenta darker) ) (blockEnd6 (magenta darker) ) (blockStart7 blue ) (blockEnd7 blue ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) + (byteArrayStart black ) + (byteArrayEnd black ) + (byteArrayStart1 black ) + (byteArrayEnd1 black ) (leftBrace black ) (rightBrace black ) ....

1 2

[Pharo-project] Issue 3247 breaks external packages
by Miguel CobÃ¡ March 15, 2011

March 15, 2011

I am trying to run Magma and uses TextConstants at: idiom. Before 3247 TextConstants was a Dictionary and the at: message works ok. But now that it is a SharedPool there is no way to use the external code without modify it before it works in Pharo 1.2. This change doesn't even tries to present the same interface to acces the Text constants as before. The TextConstants>>at: message in Pharo 1.2 is the Object>>at: method that obviously doesn't work. What is the reason of this change? Why is better than the dictionary (I suppose that reifying it is a reason)? What is the intended usage for code that uses TextConstants the dictionary access way? Specifically, code like this doesn't work anymore in Pharo1.2 self ~~ (TextConstants at: #DefaultTabsArray) and: [ self ~~ (TextConstants at: #DefaultMarginTabsArray) ] What should I do, I can't see a reopen status in the issue tracker. Should I open a new ticket? Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

3 8

Re: [Pharo-project] Issue 958 in pharo: Adding Iterable to Pharo
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Updates: Labels: -Milestone-1.3 Comment #10 on issue 958 by marcus.d...(a)gmail.com: Adding Iterable to Pharo http://code.google.com/p/pharo/issues/detail?id=958 (No comment was entered for this change.)

1 0

Re: [Pharo-project] Issue 825 in pharo: Some changes are not save to the changes file
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Updates: Labels: -Milestone-1.3 Comment #8 on issue 825 by marcus.d...(a)gmail.com: Some changes are not save to the changes file http://code.google.com/p/pharo/issues/detail?id=825 (No comment was entered for this change.)

1 0

Re: [Pharo-project] Issue 709 in pharo: Debugger highlight bug
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Updates: Labels: -Milestone-1.3 Comment #18 on issue 709 by marcus.d...(a)gmail.com: Debugger highlight bug http://code.google.com/p/pharo/issues/detail?id=709 (No comment was entered for this change.)

1 0

[Pharo-project] Issue 3629 in pharo: [Hudson] Update Hudson
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3629 by marcus.d...(a)gmail.com: [Hudson] Update Hudson http://code.google.com/p/pharo/issues/detail?id=3629 The Version provided is very old. Most plugins need a newer version.

1 1

Re: [Pharo-project] Issue 1386 in pharo: moving methods from one category to another has trouble on the last item
by pharo＠googlecode.com March 15, 2011

March 15, 2011

Updates: Status: Closed Comment #1 on issue 1386 by marcus.d...(a)gmail.com: moving methods from one category to another has trouble on the last item http://code.google.com/p/pharo/issues/detail?id=1386 Seems to work on 1.2. Please check and add a new report if this is still a problem

1 0