- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fwd: Re: Decoding bug with XMLParser ?

by Philippe Marschall

On 19.05.2010 19:35, StÃ©phane Ducasse wrote: >>> >>> >> >> Currently the semantics in Pharo are >> 0: Latin 1 >> 255: Unicode >> >> which is fun because the first 255 characters are interned and you >> therefore can't change their leadingChar. So if you're using Unicode, >> you're forced to mix leachingChars. > > so what do you suggest to have unicode as zero? Yes, the decision of Squeak 4.1 to make Unicode leadingChar 0 is an improvement. Cheers Philippe

May 19, 2010

Re: [Pharo-project] UUID on ubuntu 10.04

by David T. Lewis

That is exactly how it works: UUID>>primMakeUUID <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'> UUIDGenerator default generateBytes: self forVersion: 4. I added this to the Mantis issue: To summarize: The bug exists in some versions of libuuid on some Linux distributions. The workaround is to compile the plugin internal. The latest versions of Unix VM have the plugin compiled internally, although some users may still experience problems if they have a leftover external plugin from a prior installation. If you experience this problem, then get the latest Unix VM and delete any existing copies of the external plugin. Resolved in latest Unix VMs. The UUID plugin must be compiled internally to avoid a bug in some versions of libuuid. Hopefully this is an accurate summary. Dave On Wed, May 19, 2010 at 06:15:32PM +0200, St?phane Ducasse wrote: > I'm not sure that it is resolved. It would be good to make sure that the system does not crash > even without reporting a log. May be having a stupid UUID generator as a fallback would be good. > > Stef > > > Thanks, I marked the issue as resolved and summarized the status here: > > > > http://bugs.squeak.org/view.php?id=7358 > > > > Dave > > > > On Wed, May 19, 2010 at 09:42:28AM +0200, St?phane Ducasse wrote: > >> Apparently the student reinstalled her ubuntu from scratch (no incremental installation) and the vm did not crash > >> anymore. > >> > >> Stef > >> > >> On May 17, 2010, at 9:16 PM, St?phane Ducasse wrote: > >> > >>> I asked the student to try. > >>> > >>> Stef > >>> > >>> On May 17, 2010, at 9:06 PM, laurent laffont wrote: > >>> > >>>> On ArchLinux I have the problem when UUID is built external. Official 4.0.3.2202 Unix VM binaries on http://squeakvm.org/unix/ works well for me (UUID is internal). > >>>> > >>>> Can you try with this one click image I made once (uses 4.0.3.2202 binaries) http://lolgzs.free.fr/pharo/Pharo-1.0-OneClick.zip > >>>> > >>>> Laurent Laffont > >>>> > >>>> http://pharocasts.blogspot.com/ > >>>> http://magaloma.blogspot.com/ > >>>> > >>>> > >>>> On Mon, May 17, 2010 at 8:24 PM, St?phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >>>> I can confirm that this is exactly the same trace than the one reported by laurent (no debug file). > >>>> > >>>> Stef > >>>> On May 17, 2010, at 7:51 PM, David T. Lewis wrote: > >>>> > >>>>> On Mon, May 17, 2010 at 07:38:59PM +0200, St?phane Ducasse wrote: > >>>>>> Hi guys > >>>>>> > >>>>>> I took seaside the latest one click image and when I have to save a MC package > >>>>>> I get a core dump with UUID new:... > >>>>>> I checke the so.UUIDplugin is there and I do not understand. > >>>>>> Can somebody with a Ubuntu give a try to save something using MC and the latest seaside one click. > >>>>> > >>>>> Hi Stef, > >>>>> > >>>>> This issue is being tracked here: http://bugs.squeak.org/view.php?id=7358 > >>>>> > >>>>> It is not clear to me if the issue is resolved in the Ian's latest VM > >>>>> build, so if you or anyone else can confirm the UUID crash happening > >>>>> with this VM, that would be helpful to clarify. > >>>>> > >>>>> Dave > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2010

Re: [Pharo-project] NetNameResolver in Pharo 1.1

by Miguel Enrique CobÃ¡ Martinez

El sÃ¡b, 08-05-2010 a las 17:54 +0200, Lukas Renggli escribiÃ³: > In Pharo 1.0 there were some problems with the network stack (namely > the NetNameResolver) and the IP6 code was reverted shortly before > release, see the following issue for details: > > http://code.google.com/p/pharo/issues/detail?id=1884 > > Today I was checking with Stef for the presence of these problems in > Pharo 1.1, but we could not reproduce neither on Mac, Windows nor > Linux. Does anybody have problems with the following expressions in > Pharo 1.1? > > NetNameResolver localHostAddress. > NetNameResolver addressForName: 'www.yahoo.com'. > > Or are we doing the wrong thing to reproduce? > > Lukas Sorry for arriving late to the party :). I tried the doits from the problem on Pharo 1.0 in a Pharo Core 11364 image. I got some error, although not as severe as in Pharo 1.0. I added an issue for this http://code.google.com/p/pharo/issues/detail?id=2444 Now, I'm going to test with Magma to see if some other error shows Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

May 19, 2010

Re: [Pharo-project] impossible to move window :)

by StÃ©phane Ducasse

ok :) I do not know what I did :) On May 19, 2010, at 7:32 PM, Mariano Martinez Peck wrote: > I can. In 11367 > > On Wed, May 19, 2010 at 6:50 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > is it me or the latest beta introduced a nice behavior that make sure that you > cannot move windows anymore? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2010

Re: [Pharo-project] Fwd: Re: Decoding bug with XMLParser ?

by StÃ©phane Ducasse

>> >> > > Currently the semantics in Pharo are > 0: Latin 1 > 255: Unicode > > which is fun because the first 255 characters are interned and you > therefore can't change their leadingChar. So if you're using Unicode, > you're forced to mix leachingChars. so what do you suggest to have unicode as zero? Stef

May 19, 2010

Re: [Pharo-project] O2 in 1.1

by StÃ©phane Ducasse

On May 19, 2010, at 6:55 PM, Mariano Martinez Peck wrote: > > > On Tue, May 18, 2010 at 11:04 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On May 18, 2010, at 10:00 PM, Geert Claes wrote: > > > > > Just loaded O2 in 1.1 and when I start it I get the warning "The method > > Collection asSortedArray has been deprecated. Use asArray sort" > > > > How do I actually change my default system browser back? > > Look at ToolSet > > But that sucks completly. Because the only way to change it is to subclass and override. > If you want to know more why it sucks, read this thread: ok I was thinking that this was > > SystemBrowser default: OBSystemBrowserAdaptor. Stef > > http://forum.world.st/Questions-about-ToolSet-td1460544.html#a1460544 > > If someone is willing to fix it, welcome!! > > you can also click on the window right icons and get the menu and select choose new default browser. > > > Yes, exactly. In the right icon of a system browser -> "Choose new default browser" > > By code SystemBrowser default: OBSystemBrowserAdaptor. > > Change OBSystemBrowserAdaptor for what you want. > > Cheers > > Mariano > > Would be good then to fix the deprecated use. > > Stef > > > -- > > View this message in context: http://forum.world.st/O2-in-1-1-tp2221821p2221821.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2010

[Pharo-project] Fwd: [Lsehub-staff] Why the hacking friday is good :)

by StÃ©phane Ducasse

a really cool talk... Stef PS: the friday afternoon in our team we just code together or do stuff that should not get done automatically :) Begin forwarded message: > From: Damien Pollet <damien.pollet(a)inria.fr> > Date: May 19, 2010 7:04:43 PM GMT+02:00 > To: âlsehubâ <lsehub-staff(a)lists.gforge.inria.fr> > Subject: [Lsehub-staff] Why the hacking friday is good :) > Reply-To: notre liste <lsehub-staff(a)lists.gforge.inria.fr> > > http://everywhereelse.wordpress.com/2010/05/14/watch-this-when-youre-done-w… > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > > > > _______________________________________________ > Lsehub-staff mailing list > Lsehub-staff(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/lsehub-staff

May 19, 2010

Re: [Pharo-project] impossible to move window :)

by Mariano Martinez Peck

I can. In 11367 On Wed, May 19, 2010 at 6:50 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > is it me or the latest beta introduced a nice behavior that make sure that > you > cannot move windows anymore? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2010

Re: [Pharo-project] Bug? ParagraphEditor do-its are not following the expected method lookup

by Mariano Martinez Peck

Hi Carla. I would like to help you, but I have no idea. I could reproduce it. Maybe Lukas, Igor, Eliot etc can help you. I have no idea. Cheers Mariano 2010/5/18 Carla F. Griggio <carla.griggio(a)gmail.com> > Hi everybody! > > Well, maybe you are already aware of this... maybe not. I tried to find an > issue about this and unless I didn't think of the right keywords, it's not > there. > > I was debugging a template method and sudenly I found myself spending ours > trying to find out why I got different results when printing the result of a > message sent to super and when steping into that message and printing the > (same) result there. > > Imagine this simple situation (I attatch the complete code and some tests > so you can reproduce this): > > AverageTotalization inherits from Totalization. > WeightedAverageTotalization inherits from AverageTotalization. > > Totalization>>total > ^self summatory > > AverageTotalization>>total > ^*(**super total)* / self denominator > > AverageTotalization>> denominator > ^values size > > WeightedAverageTotalization>> denominator > "Weights is a dictionary" > ^self weights values sum > > > If I debug aWeightedAverateTotalization total and try to print *super > total* in the debugger ParagraphEditor, I'll get this result: > > (self summatory / self denominator) > > instead of just: > > self summatory > > This only happens when I print or inspect or other do-its in the debugger > window. The method lookup works OK when just evaluating the code (the tests > I made are green). > > I think that when you print or inspect (etc) *super total*, the evaluation > context takes WeightedAverageTotalization class instead of > AverageTotalization, so when total is sent to super under that context, the > code is looked up on AverageTotalization instead of Totalization. > Could that be possible? Am I thinking right? > > I spent a *while* chasing this bug, and I found a solution, but I don't > know if it's OK or if it's the best. It's simple and it seems to work. I > tested it in the last PharoCore1.1 unstable image. > > I attach some code to reproduce the error (you'll get a halt when you run > the test, read the comments, the problem is clear when you run the weighted > average test), and the code that fixes this. > > If you confirm that this was not a known issue, I'll register it on the > issue tracker with both these attachments. > > If it was a known issue... well, I learned :) (I think XD) > > Cheers! > > Carla. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2010

Re: [Pharo-project] Fwd: Re: Decoding bug with XMLParser ?

by Philippe Marschall

On 19.05.2010 07:58, Damien Pollet wrote: > 2010/5/19 Levente Uzonyi <leves(a)elte.hu>: >> Another "hard to quote" message, but I hope my answer will be clear. >> The "problem" is that in Pharo the leadingChar for unicode characters is >> still 255. This was changed in Squeak 4.1 to 0. So in Squeak 4.1: >> (Unicode value: 8230) codePoint. "===> 8230" >> >> While in Pharo it's: >> (Unicode value: 8230) codePoint. "===> 1069555750" >> (Character value: 1069555750) charCode. "===> 8230" >> (Character value: 1069555750) leadingChar. "===> 255" >> >> So using #charCode instead of #codePoint is the solution. > > What about updating the leadingChar in Pharo to match Squeak? (I know > it's not the correct solution to the present problem but it's these > kinds of sneaky differences between platform that make life difficult) > > What's the semantic difference between picking 0 or 255? Is one more > correct than the other? > Currently the semantics in Pharo are 0: Latin 1 255: Unicode which is fun because the first 255 characters are interned and you therefore can't change their leadingChar. So if you're using Unicode, you're forced to mix leachingChars. Cheers Philippe

May 19, 2010