January 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ENH] Literal Byte Arrays

by Lukas Renggli

> so do I understand correctly that your point is to replace > asByteArray by #[] Yes, instead of writing #( 1 2 3 ) asByteArray you write #[ 1 2 3 ] Which is much faster and saves memory, as no conversion and no copying happens at runtime. All Smalltalk dialects (with the exception of GemStone) support this syntax. Pharo should have it too. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 30, 2009

Re: [Pharo-project] [ENH] Literal Byte Arrays

by StÃ©phane Ducasse

Lukas so do I understand correctly that your point is to replace asByteArray by #[] Stef On Jan 30, 2009, at 8:47 AM, Lukas Renggli wrote: > I committed a patch that adds literal byte arrays to Pharo, with the > same syntax as most other Smalltalk do (VW, VASt, GST). > > http://code.google.com/p/pharo/issues/detail?id=468 > > I would appreciate if somebody could review the change, as it would be > very useful for Seaside and solves reoccurring headaches. In my image > I have almost 50 places where even the Pharo base code could profit > from this extension, these places can be identified using the search > expression: > > `#literal asByteArray > > I can provide a refactoring at a later point, if desired. > > The change is simple and loads through Monticello, even if this is > modifying the scanner on the fly. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 30, 2009

Re: [Pharo-project] Using pharo in a course?

by StÃ©phane Ducasse

Not for newbies. People really look at the package before its contents. We should give them a chance. Stef On Jan 29, 2009, at 6:59 PM, Gary Chambers wrote: > Indeed... though that does make you focus on the underlying stuff > and give > an opportunity for changing the image to improve your lot! > > ----- Original Message ----- > From: "Michael Rueger" <m.rueger(a)acm.org> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Thursday, January 29, 2009 5:13 PM > Subject: Re: [Pharo-project] Using pharo in a course? > > >> Gary Chambers wrote: >> >>> nicer UI ( ;-) )... >> >> Never underestimate the repulsive (or is it revolting? ;-) ) effect >> of >> the original Squeak UI on beginners... >> >> Michael >> >> _______________________________________________ >> 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 >

Jan. 30, 2009

Re: [Pharo-project] [Vm-dev] newDelta >0 failed in sqUnixMemory

by Damien Cassou

On Fri, Jan 30, 2009 at 9:00 AM, Andreas Raab <andreas.raab(a)gmx.de> wrote: > Since you're compiling the VM yourself, you might want to add a guard that > catches the condition and prints out the environmental values (oldLimit, > delta, newSize, newDelta). I would suspect that this is a signed/unsigned > issue with memory being allocated somewhere close to the 2GB barrier and > then flipping from positive to negative. Since newSize and newDelta are > declared int, this could easily happen. I've just downgraded gcc to 3.4 (instead of 4.3.2) and it seems to work fine. Do you want me to do more testing with the 4.3.2 version? -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 30, 2009

[Pharo-project] [ENH] Literal Byte Arrays

by Lukas Renggli

I committed a patch that adds literal byte arrays to Pharo, with the same syntax as most other Smalltalk do (VW, VASt, GST). http://code.google.com/p/pharo/issues/detail?id=468 I would appreciate if somebody could review the change, as it would be very useful for Seaside and solves reoccurring headaches. In my image I have almost 50 places where even the Pharo base code could profit from this extension, these places can be identified using the search expression: `#literal asByteArray I can provide a refactoring at a later point, if desired. The change is simple and loads through Monticello, even if this is modifying the scanner on the fly. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 30, 2009

[Pharo-project] newDelta >0 failed in sqUnixMemory

by Damien Cassou

Hi, with a recent stock pharo image and a new VM compiled from svn on Linux, I always get squeak: /tmp/squeak-svn/platforms/unix/vm/sqUnixMemory.c:172: uxGrowMemoryBy: Assertion `newDelta >= 0' failed. Aborted This does not happen on Squeak 3.9 nor 3.10. This did not happen yesterday when I was on Ubuntu Hardy. Now, I'm on Intrepid, GCC 4.3.2 and it crashes after 3 seconds of work on any Pharo image. You may want to know that to compile the vm, I was obliged to change sqUnixFBDevMousePS2.c to make use of the 'write(2)' return value because my compiler didn't want to compile if write(2) return value was unused. -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 30, 2009

Re: [Pharo-project] OB Enhancements universe definition broken

by Damien Cassou

On Thu, Jan 29, 2009 at 9:52 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Running ScriptLoader loadOB fails at some point because it tries to load > > http://source.wiresong.ca/ob/OB-Enhancements-dr.291 > instead of http://source.wiresong.ca/ob/OB-Enhancements-dr.291.mcz Fixed, thank you. -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 30, 2009

Re: [Pharo-project] Call for UI gripes

by Adrian Lienhard

Hi Gary, Thanks for the great work so far! Here some feedback... I merged Polymorph-Widgets-gvc.36 into a current Pharo image (using the default theme, Watery2). Then loaded OB. - Pre-Debugger window buttons look odd in the latest version (see screenshot) - Menu selection does not honor enter, only mouse click. Try doit "1 aa" then select an item from the menu by keyboard and hit enter. Nothing happens (not sure, though, if this is related to Polymorph) - do not show popup windows in task bar, only main windows - Buttons: the text on the blue buttons is a bit hard to read. Furthermore, In the OB Browser there are two types of blue buttons. It would be nice to have a consistent style for buttons. - the style of tooltips (see screenshot) might be improved (- in the preference browser, which by the way looks great compared to the old one, the button "theme..." os obsolete.) Cheers, Adrian On Jan 29, 2009, at 17:56 , Gary Chambers wrote: > Anything that anyone thinks could be improved? > Happy to consider things... just would be nice to have a central > point for > moving forward with Polymorph (in particular) or other tools... > > There is a possibility of open-source release of the PackageListTool > (http://www.flickr.com/photos/12018791@N06/2616669616/in/set-721576016593932… > ) > if there is any interest. > > Regards, Gary. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 29, 2009

[Pharo-project] OB Enhancements universe definition broken

by Adrian Lienhard

Running ScriptLoader loadOB fails at some point because it tries to load http://source.wiresong.ca/ob/OB-Enhancements-dr.291 instead of http://source.wiresong.ca/ob/OB-Enhancements-dr.291.mcz Adrian ___________________ http://www.adrian-lienhard.ch/

Jan. 29, 2009

Re: [Pharo-project] Call for UI gripes

by Gary Chambers

Well, a contemporary look will always drive the computer harder... Don't really find it a problem here though. Main PC is a 2.8MHzQuadCore, lappie is a 1.7MHz Centrino. Guess you might benefit from faster hardware. The SoftSqueak theme seems to be the fastest overall, curious since nicer looking than StandardSqueak (which is, essentially, a pass-through replication of the original code). I guess a poll of some kind of benchmark for all on the list may be in order... Thanks for the support. Regards, Gary. ----- Original Message ----- From: Mariano Martinez Peck To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, January 29, 2009 6:06 PM Subject: Re: [Pharo-project] Call for UI gripes Gary: First of all, thanks for your excellent work. I really like Polymorph and I use it as my default "theme". Very very impressive. However, squeak seems to be a bit slower with it. For example, in SqueakDBX we are 4 developers. Two of them cannot use it because is slower enough to loose their patient. I am still newbie in squeak so I really don't know the resasons of this. Perhaps this is a morphic thing and nothing about Polymorph. If this is the case, sorry. Please, continue with your work. I really enjoy Polymorph and happy to be the default in pharo. Cheers, Mariano On Thu, Jan 29, 2009 at 2:56 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: Anything that anyone thinks could be improved? Happy to consider things... just would be nice to have a central point for moving forward with Polymorph (in particular) or other tools... There is a possibility of open-source release of the PackageListTool (http://www.flickr.com/photos/12018791@N06/2616669616/in/set-721576016593932…) if there is any interest. Regards, Gary. _______________________________________________ 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

Jan. 29, 2009