- Pharo-dev - lists.pharo.org

Re: [Pharo-project] about name for logging message

by Schwab,Wilhelm K

Stef, I'm not really sure what you are trying to do, but in Dolphin, I created a "runtime transcript" that would dump output into a file. My runtime session manager sub-classes all set the global Transcript to point to the (hopefully/intended-to-be thread-safe) file stream. I later built an application-specific logging facility that was configurable both in verbosity and in whether it went to the file or to the debug monitor (OutputDebugString()). Speaking of OutputDebugString(), I had so many uses of it, that I created something analogous in Pharo. It notes the OS and sends ouput to syslog() on Linux. Object Arts planned to remove Transcript>>show: at one point. IIRC, they did not actually remove it, which was fine with me, because it meant that I didn't have to be bothered adding it myself :) I *think* they added a new global stream, Trace, that wrote to the transcript, so one would use things like Trace print:someObject; cr. to log. And that stream could, of course, be connected to a file for deployed executables. Just some random thoughts... Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Saturday, November 05, 2011 10:35 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] about name for logging message yes could be a good candidate. let us see if other suggestions arrive Stef On Nov 5, 2011, at 2:38 PM, Norbert Hartl wrote: > > Am 05.11.2011 um 12:50 schrieb StÃ©phane Ducasse: > >> Hi guys >> >> I introduce >> log to replace Transcript show: â¦ >> logCr and crLog >> >> Now stupidly I did not notice that it will capture log on number :( and also on collection, >> >> So any suggestion of what would be a nice logging message? >> short and cool. >> > How about trace? > > Norbert

Nov. 5, 2011

Re: [Pharo-project] about name for logging message

by StÃ©phane Ducasse

yes could be a good candidate. let us see if other suggestions arrive Stef On Nov 5, 2011, at 2:38 PM, Norbert Hartl wrote: > > Am 05.11.2011 um 12:50 schrieb StÃ©phane Ducasse: > >> Hi guys >> >> I introduce >> log to replace Transcript show: â¦ >> logCr and crLog >> >> Now stupidly I did not notice that it will capture log on number :( and also on collection, >> >> So any suggestion of what would be a nice logging message? >> short and cool. >> > How about trace? > > Norbert

Nov. 5, 2011

Re: [Pharo-project] Keymapping Questions

by Sean P. DeNigris

Guillermo Polito wrote: > > This should not happen in the bleeding edge :) > Yes, I updated to bleedingEdge and this is fixed. I will keep playing... -- View this message in context: http://forum.world.st/Keymapping-Questions-tp3990667p3993303.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 5, 2011

Re: [Pharo-project] about name for logging message

by Norbert Hartl

Am 05.11.2011 um 12:50 schrieb StÃ©phane Ducasse: > Hi guys > > I introduce > log to replace Transcript show: â¦ > logCr and crLog > > Now stupidly I did not notice that it will capture log on number :( and also on collection, > > So any suggestion of what would be a nice logging message? > short and cool. > How about trace? Norbert

Nov. 5, 2011

[Pharo-project] about name for logging message

by StÃ©phane Ducasse

Hi guys I introduce log to replace Transcript show: â¦ logCr and crLog Now stupidly I did not notice that it will capture log on number :( and also on collection, So any suggestion of what would be a nice logging message? short and cool. Stef

Nov. 5, 2011

Re: [Pharo-project] UUID comparaison is Incorrect

by StÃ©phane Ducasse

Thanks norbert. You see this was a kind of exerciseâ¦ to see if people can get a bit more involved. I could have simply introduce the fix but I want people to understand that there are a lot of little trivial things that can get done and it will help the system. So thank :) :) On Nov 5, 2011, at 11:20 AM, Norbert Hartl wrote: > And I would rather like to see another implementation like > > < aMagnitude > "Answer whether the receiver is less than the argument." > > (self size = aMagnitude size) ifFalse: [ > ^ self size < aMagnitude size ]. > 1 to: self size do: [:i | > (self at: i) = (aMagnitude at: i) ifFalse: [ > ^ (self at: i) < (aMagnitude at: i) ]]. > ^false. > > Norbert > > Am 04.11.2011 um 21:13 schrieb StÃ©phane Ducasse: > >> I was thinking that we should get the same bug for you UUID >> because the code right now is >> >> < aMagnitude >> "Answer whether the receiver is less than the argument." >> >> 1 to: self size do: [:i | >> (self at: i) < (aMagnitude at: i) ifTrue: [^true]]. >> ^false. >> >> >>>> |a b| >>>> a := UUID fromString: '0608b9dc-02e4-4dd0-9f8a-ea45160df641'. >>>> b := UUID fromString: 'e85ae7ba-3ca3-4bae-9f62-cc2ce51c525e'. >>>> (a > b) = (b > a) >> >> returns true and this looks wrong :) >> >> What do you think? >> >> Stef >> >> >> Begin forwarded message: >> >>> From: Alan Knight <knight(a)acm.org> >>> Subject: Re: [vwnc] UUID Sorting Incorrect >>> Date: November 1, 2011 3:19:23 PM GMT+01:00 >>> To: Runar Jordahl <runar.jordahl(a)gmail.com> >>> Cc: vwnc(a)cs.uiuc.edu >>> Reply-To: knight(a)acm.org >>> >>> Thanks. Created AR 64162 >>> >>>> >>>> Runar Jordahl >>>> 25 October, 2011 7:13 AM >>>> >>>> >>>> Class UUID is included in beta in VisualWorks 7.8. It seems like #< is >>>> implemented incorrect. If you evaluate the statement below it answers >>>> true: >>>> >>>> |a b| >>>> a := UUID fromString: '0608b9dc-02e4-4dd0-9f8a-ea45160df641'. >>>> b := UUID fromString: 'e85ae7ba-3ca3-4bae-9f62-cc2ce51c525e'. >>>> (a > b) = (b > a) >>>> >>>> The fix is to change the method to this: >>>> >>>> < aMagnitude >>>> "Answer whether the receiver is less than the argument. Add an >>>> initial size check, in anticipation of greater than 128-bit >>>> Smalltalk-specific UUID type." >>>> >>>> | ss ms | >>>> >>>> ss := self size. >>>> ms := aMagnitude size. >>>> ss < ms >>>> ifTrue: [^true] >>>> ifFalse: [ >>>> ss > ms >>>> ifTrue: [^false] >>>> ifFalse: [ >>>> 1 to: self size do: [:i | >>>> (self at: i) < (aMagnitude at: i) ifTrue: [^true]. >>>> (self at: i) > (aMagnitude at: i) ifTrue: [^false]]. >>>> ^false]] >>>> >>>> >>>> Runar Jordahl >>>> blog.epigent.com >>>> _______________________________________________ >>>> vwnc mailing list >>>> vwnc(a)cs.uiuc.edu >>>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>> _______________________________________________ >>> vwnc mailing list >>> vwnc(a)cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> >

Nov. 5, 2011

Re: [Pharo-project] UUID comparaison is Incorrect

by Norbert Hartl

And I would rather like to see another implementation like < aMagnitude "Answer whether the receiver is less than the argument." (self size = aMagnitude size) ifFalse: [ ^ self size < aMagnitude size ]. 1 to: self size do: [:i | (self at: i) = (aMagnitude at: i) ifFalse: [ ^ (self at: i) < (aMagnitude at: i) ]]. ^false. Norbert Am 04.11.2011 um 21:13 schrieb StÃ©phane Ducasse: > I was thinking that we should get the same bug for you UUID > because the code right now is > > < aMagnitude > "Answer whether the receiver is less than the argument." > > 1 to: self size do: [:i | > (self at: i) < (aMagnitude at: i) ifTrue: [^true]]. > ^false. > > >>> |a b| >>> a := UUID fromString: '0608b9dc-02e4-4dd0-9f8a-ea45160df641'. >>> b := UUID fromString: 'e85ae7ba-3ca3-4bae-9f62-cc2ce51c525e'. >>> (a > b) = (b > a) > > returns true and this looks wrong :) > > What do you think? > > Stef > > > Begin forwarded message: > >> From: Alan Knight <knight(a)acm.org> >> Subject: Re: [vwnc] UUID Sorting Incorrect >> Date: November 1, 2011 3:19:23 PM GMT+01:00 >> To: Runar Jordahl <runar.jordahl(a)gmail.com> >> Cc: vwnc(a)cs.uiuc.edu >> Reply-To: knight(a)acm.org >> >> Thanks. Created AR 64162 >> >>> >>> Runar Jordahl >>> 25 October, 2011 7:13 AM >>> >>> >>> Class UUID is included in beta in VisualWorks 7.8. It seems like #< is >>> implemented incorrect. If you evaluate the statement below it answers >>> true: >>> >>> |a b| >>> a := UUID fromString: '0608b9dc-02e4-4dd0-9f8a-ea45160df641'. >>> b := UUID fromString: 'e85ae7ba-3ca3-4bae-9f62-cc2ce51c525e'. >>> (a > b) = (b > a) >>> >>> The fix is to change the method to this: >>> >>> < aMagnitude >>> "Answer whether the receiver is less than the argument. Add an >>> initial size check, in anticipation of greater than 128-bit >>> Smalltalk-specific UUID type." >>> >>> | ss ms | >>> >>> ss := self size. >>> ms := aMagnitude size. >>> ss < ms >>> ifTrue: [^true] >>> ifFalse: [ >>> ss > ms >>> ifTrue: [^false] >>> ifFalse: [ >>> 1 to: self size do: [:i | >>> (self at: i) < (aMagnitude at: i) ifTrue: [^true]. >>> (self at: i) > (aMagnitude at: i) ifTrue: [^false]]. >>> ^false]] >>> >>> >>> Runar Jordahl >>> blog.epigent.com >>> _______________________________________________ >>> vwnc mailing list >>> vwnc(a)cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> _______________________________________________ >> vwnc mailing list >> vwnc(a)cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >

Nov. 5, 2011

[Pharo-project] [update 1.4] #14216

by StÃ©phane Ducasse

14216 ----- - Issue 4963: Debugger crashes the image when the selector is > or >>. Thanks Benjamin van ryseghem and nicolas cellier. http://code.google.com/p/pharo/issues/detail?id=4963 - Issue 4906: crLog http://code.google.com/p/pharo/issues/detail?id=4906 - Issue 4953: Toggle break on entry is broken. Thanks nicolas cellier. http://code.google.com/p/pharo/issues/detail?id=4953 - Issue 4962: TaskList open on cmd+shift+letf/right. Thansk Benjamin van ryseghem. http://code.google.com/p/pharo/issues/detail?id=4962 Stef

Nov. 5, 2011

Re: [Pharo-project] UUID comparaison is Incorrect

by Norbert Hartl

Am 04.11.2011 um 21:13 schrieb StÃ©phane Ducasse: > I was thinking that we should get the same bug for you UUID > because the code right now is > > < aMagnitude > "Answer whether the receiver is less than the argument." > > 1 to: self size do: [:i | > (self at: i) < (aMagnitude at: i) ifTrue: [^true]]. > ^false. > > >>> |a b| >>> a := UUID fromString: '0608b9dc-02e4-4dd0-9f8a-ea45160df641'. >>> b := UUID fromString: 'e85ae7ba-3ca3-4bae-9f62-cc2ce51c525e'. >>> (a > b) = (b > a) > > returns true and this looks wrong :) > > What do you think? > Come on, this is not a problem for UUIDs where all digits are the same. So just fix the comment "Answer whether any digit of the receiver is less than the digit of the argument at the same position." done! Norbert > Stef > > > Begin forwarded message: > >> From: Alan Knight <knight(a)acm.org> >> Subject: Re: [vwnc] UUID Sorting Incorrect >> Date: November 1, 2011 3:19:23 PM GMT+01:00 >> To: Runar Jordahl <runar.jordahl(a)gmail.com> >> Cc: vwnc(a)cs.uiuc.edu >> Reply-To: knight(a)acm.org >> >> Thanks. Created AR 64162 >> >>> >>> Runar Jordahl >>> 25 October, 2011 7:13 AM >>> >>> >>> Class UUID is included in beta in VisualWorks 7.8. It seems like #< is >>> implemented incorrect. If you evaluate the statement below it answers >>> true: >>> >>> |a b| >>> a := UUID fromString: '0608b9dc-02e4-4dd0-9f8a-ea45160df641'. >>> b := UUID fromString: 'e85ae7ba-3ca3-4bae-9f62-cc2ce51c525e'. >>> (a > b) = (b > a) >>> >>> The fix is to change the method to this: >>> >>> < aMagnitude >>> "Answer whether the receiver is less than the argument. Add an >>> initial size check, in anticipation of greater than 128-bit >>> Smalltalk-specific UUID type." >>> >>> | ss ms | >>> >>> ss := self size. >>> ms := aMagnitude size. >>> ss < ms >>> ifTrue: [^true] >>> ifFalse: [ >>> ss > ms >>> ifTrue: [^false] >>> ifFalse: [ >>> 1 to: self size do: [:i | >>> (self at: i) < (aMagnitude at: i) ifTrue: [^true]. >>> (self at: i) > (aMagnitude at: i) ifTrue: [^false]]. >>> ^false]] >>> >>> >>> Runar Jordahl >>> blog.epigent.com >>> _______________________________________________ >>> vwnc mailing list >>> vwnc(a)cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> _______________________________________________ >> vwnc mailing list >> vwnc(a)cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >

Nov. 5, 2011

[Pharo-project] Call for help for reviewing code

by StÃ©phane Ducasse

Hi guys there are plenty of bugs fixes that are waiting for review in the bug tracker. If each of us take two we will get really done fast. So can you give a hand and have a look the fixes. Stef

Nov. 5, 2011