- Pharo-dev - lists.pharo.org

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

by Bill Schwab

Lukas, I had pretty much resigned to going without this - not sure why given how much I grip about other stuff :) There are indeed efficiency considerations, but it's also a big step in compatibility. THANKS!!! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> renggli(a)gmail.com 01/30/09 4:55 AM >>> > 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 _______________________________________________ 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. Here is the result of: fprintf(stderr, "oldLimit=%p\ndelta=%d\nnewSize=%d\nnewDelta=%d\n"); oldLimit=0x80562b8 delta=-1077506096 newSize=0 newDelta=423027548 squeak: /tmp/squeak-svn/platforms/unix/vm/sqUnixMemory.c:175: uxGrowMemoryBy: Assertion `newDelta >= 0' failed. Does it help? -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 30, 2009

Re: [Pharo-project] Plugin organization

by Michael Rueger

bryce(a)kampjes.demon.co.uk wrote: > But Monticello packages are just a naming scheme. yes and no. A package is defined using the name and string matching, but a package is a package. > Your statement: "That would also allow to simply load all plugins into > a VMMaker image by using a package 'Plugin'.". Seems to indicate to > me that using the naming convention you suggested would lead to > all the packages being part of a single Monticello package. Hmm, yes and no again ;-) But I now I see what you are saying... Being able to load all plugin packages by defining a "meta" package "Plugin" exploits the string matching nature of Monticello. This "meta" package would be simply a convenience for loading, it should not, or rather must not, be stored, ever. Anyways, my proposal was really more about a naming convention for Plugin packages. The same convention could also be applied to test packages btw to avoid all this very "creative" naming, patching the "test" somewhere into the category name. Michael

Jan. 30, 2009

[Pharo-project] Multilingual tests

by Michael Rueger

Hi all, are there any other tests available for the Multilingual stuff other than "MultilingualTests-TextConversion"? Would like to avoid re-inventing the wheel... Michael

Jan. 30, 2009

Re: [Pharo-project] Call for UI gripes

by Adrian Lienhard

Hi Gary, On Jan 30, 2009, at 13:10 , GARY CHAMBERS wrote: > Buttons - after loading you should reselect your theme to initialize > the forms used for square button corners. ok, works. > menu selection - not sure what you mean. Is it a menu or a popup > choice (in which case spacebar should be used to choose option since > enter is likely to activate the default button in the dialog) ah, I didn't know. Indeed, spacebar works. > Dialogs - dialogs are tied to their originating window so will > surface if the window is selected. I guess you want not to show > dialogs in taskbar (maybe a preference, definitely not one-decision- > fits-all) yes, I think dialogs do not need to appear in the taskbar to avoid clutter, but that's not critical. > Hard to read text - much better if you use a FreeType font! ok (we will add default freetype fonts to Pharo) > OB buttons - David and I will get there eventually! > > Tooltips - in what way? Making beziers from polygon morph would be > nice and smooth, just tricky to implement I thought that tooltips like the ones you usually see (rectangle with light yellow background color) would be nicer than the balloon. > Prefs theme - I deliberately didn't touch which buttons though I'll > probably remove it next Feel free to do so if you like to get rid of them. Cheers, Adrian > > Thanks for feedback. > Regards, Gary > > > > ________________________________ > From: Adrian Lienhard <adi(a)netstyle.ch> > To: Pharo-project(a)lists.gforge.inria.fr > Sent: Thursday, 29 January, 2009 9:37:14 PM > Subject: Re: [Pharo-project] Call for UI gripes > > 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 > _______________________________________________ > 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 David T. Lewis

On Fri, Jan 30, 2009 at 09:14:33AM +0100, Damien Cassou wrote: > > 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, Yes, it would be helpful if you could find out more about what is causing the bug when using gcc 4.3.2. It's probably the int declarations as Andreas suggests, and it would be good if you can confirm this. Thanks, Dave

Jan. 30, 2009

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

by Michael Rueger

Michael Rueger wrote: > Provoost, P (Paul) wrote: >> I have the same problem when compiling the vm on OpenSolaris 2008-11 >> using the SUN compilers. So please do some more testing with the >> 4.3.2. version, after all we cannot stick to old compilers, can we? > > Some VM maintainers can ;-) > Windows is still officially compiled with GCC 2.95... John McIntosh and I actually spent some time a few ago compiling VMs on Windows and MacOS with the newest GCCs and ran into a bunch of problems, especially concerning performance. I had to put the work on the back burner for now, but switching to newer compilers will take a bit of extra work at some point. Michael

Jan. 30, 2009

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

by Michael Rueger

Provoost, P (Paul) wrote: > I have the same problem when compiling the vm on OpenSolaris 2008-11 > using the SUN compilers. So please do some more testing with the > 4.3.2. version, after all we cannot stick to old compilers, can we? Some VM maintainers can ;-) Windows is still officially compiled with GCC 2.95... Michael

Jan. 30, 2009

Re: [Pharo-project] Call for UI gripes

by GARY CHAMBERS

Buttons - after loading you should reselect your theme to initialize the forms used for square button corners. menu selection - not sure what you mean. Is it a menu or a popup choice (in which case spacebar should be used to choose option since enter is likely to activate the default button in the dialog) Dialogs - dialogs are tied to their originating window so will surface if the window is selected. I guess you want not to show dialogs in taskbar (maybe a preference, definitely not one-decision-fits-all) Hard to read text - much better if you use a FreeType font! OB buttons - David and I will get there eventually! Tooltips - in what way? Making beziers from polygon morph would be nice and smooth, just tricky to implement Prefs theme - I deliberately didn't touch which buttons though I'll probably remove it next Thanks for feedback. Regards, Gary ________________________________ From: Adrian Lienhard <adi(a)netstyle.ch> To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, 29 January, 2009 9:37:14 PM Subject: Re: [Pharo-project] Call for UI gripes 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. 30, 2009

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

by Provoost, P (Paul)

I have the same problem when compiling the vm on OpenSolaris 2008-11 using the SUN compilers. So please do some more testing with the 4.3.2. version, after all we cannot stick to old compilers, can we? Regards, Paul Provoost. 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. Damien Cassou wrote: > 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 _____________________________________________________________ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _____________________________________________________________

Jan. 30, 2009