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

[Pharo-project] About mime encoding

by StÃ©phane Ducasse

Hi in the squeak trunk jcg in collections-jcg.124 did mimeEncode: aStream "Return a ReadWriteStream of characters. The data of aStream is encoded as 65 innocuous characters. (See class comment). 3 bytes in aStream goes to 4 bytes in output." | me | >> aStream position: 0. me := self new dataStream: aStream. me mimeStream: (ReadWriteStream on: (String new: aStream size + 20 * 4 // 3)). me mimeEncode. me mimeStream position: 0. ^ me mimeStream I would like to know if one of you agree on that. Thanks Stef

Jan. 15, 2010

[Pharo-project] [update 1.1] #11161

by Marcus Denker

11161 ----- Issue 765: Menu must not be zero size Issue 1793: Remove SqueakClipBoard Issue 1790: basicShallowCopy should be removed -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 15, 2010

[Pharo-project] ConfigurationOfNile ready but failing and error tests

by Mariano Martinez Peck

Hi folks: I created a ConfigurationOfNile that you can find in MetacelloRepository. The weird thing is that I need to load first the tests (before Base and Clients) because otherwise there is a compile error with traits when trying to load Nile-Clients. To install it: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfNile'; load. ((Smalltalk at: #ConfigurationOfNile) project version: '1.0') load The other problem is that there are 3 failures and 11 errors. I attach screenshot. Can someone fix them ? (even if the solution is to remove them). Take into account that with this configuration, I don't use Nile-All at all. Cheers Mariano

Jan. 15, 2010

Re: [Pharo-project] MC case sensitity and sub-packages

by Schwab,Wilhelm K

Stef, I am doing some housekeeping toward building a new image. Changes such as below have allowed me to get Migrate into an almost-releasable state. One of its jobs is to look for code that is at risk of being lost, and that feature is detecting a LOT of code that should be safe; it is probably due to the extra packages. I had hoped that I could safely avoid the "double save" problem, but this is even worse than that :( Absent a simple solution, the answer is to delete DolphinCompatibility and others. The next question is then: will I have problems with dependencies between the sub-packages? I am wondering whether there could be problems saving separate packages like DolphinCompatibility-Streams DolphinCompatibility-ODBC when DolphinCompatibility would be perfectly happy. Does that make sense? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Wednesday, January 13, 2010 2:40 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] MC case sensitity and sub-packages On Jan 13, 2010, at 1:39 AM, Schwab,Wilhelm K wrote: > Brian and others have told me that I could expect to define packages > such as > > DolphinCompatibility-ODBC > DolphinCompatibility-Streams > > and save them all using DolphinCompatibility, or save just one specific part by giving the full name, such as DolphinCompatibility-ODBC. I was unable to make it work reliably, and I think I might have just figured out why. I really encourage you to save them as separate packages if you want to load and save them all build a metacelloConfig (not difficult and worth). don;t define a package DolphinCompatibility in addition (else you will get in trouble because your classes will be saved somehow twice)., I hate this pattern matching behavior. > Assertion: package names and class names must agree up to case; method categories (*packageName-etc) appear to be more forgiving. > > It further appears that once one messes up by naming a category and package Dolphincompatibility instead of DolphinCompatibility, the only way to fix it is to delete the working copy of the package and re-create it with the correct case after renaming the category, or something like that. probably I do not like that part of the system > > Does that sound right? Am I missing something that might cost me later? > > Bill > > > _______________________________________________ > 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. 15, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by Laval Jannik

Hi, Thank you for your comment, I will try this. Cheers Jannik On Jan 15, 2010, at 12:06 , Levente Uzonyi wrote: > On Fri, 15 Jan 2010, Mariano Martinez Peck wrote: > >> On Fri, Jan 15, 2010 at 10:51 AM, Laval Jannik <jannik.laval(a)inria.fr>wrote: >> >>> Hi, >>> >>> In some case I need to run my VM with more memory. >>> For now, I use the parameter "-memory" when I run the VM. >>> >>> Is it possible to define this value in the image ? >>> > > IIRC -memory allocates a fixed size memory chuck under unix and keeps it > while the vm is running, -mmap is a better approach under unix. > >> >> >> I think you can do something like: >> >> SmalltalkImage current >> vmParameterAt: 5 put: 100000; >> vmParameterAt: 6 put: 35000; >> vmParameterAt: 24 put: 16 * 1024 * 1024; >> vmParameterAt: 25 put: 8 * 1024 * 1024. >> > > These are parameters for the GC, so are irrelevant here. > >> >> But...I am not sure how to know each parameter number what exactly is. Do >> you know where I can get that information? >> > > See the comment in SmalltalkImage >> #vmParameterAt: > > > Levente > >> To see your current data I think you can do: >> >> SmalltalkImage current getVMParameters >> >> >> Cheers >> >> Mariano >> >> Then I can use it in a script. >>> >>> Cheers >>> >>> >>> --- >>> Jannik Laval >>> --- >>> >>> >>> _______________________________________________ >>> 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. 15, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by Levente Uzonyi

On Fri, 15 Jan 2010, Mariano Martinez Peck wrote: > On Fri, Jan 15, 2010 at 10:51 AM, Laval Jannik <jannik.laval(a)inria.fr>wrote: > >> Hi, >> >> In some case I need to run my VM with more memory. >> For now, I use the parameter "-memory" when I run the VM. >> >> Is it possible to define this value in the image ? >> IIRC -memory allocates a fixed size memory chuck under unix and keeps it while the vm is running, -mmap is a better approach under unix. > > > I think you can do something like: > > SmalltalkImage current > vmParameterAt: 5 put: 100000; > vmParameterAt: 6 put: 35000; > vmParameterAt: 24 put: 16 * 1024 * 1024; > vmParameterAt: 25 put: 8 * 1024 * 1024. > These are parameters for the GC, so are irrelevant here. > > But...I am not sure how to know each parameter number what exactly is. Do > you know where I can get that information? > See the comment in SmalltalkImage >> #vmParameterAt: Levente > To see your current data I think you can do: > > SmalltalkImage current getVMParameters > > > Cheers > > Mariano > > Then I can use it in a script. >> >> Cheers >> >> >> --- >> Jannik Laval >> --- >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Jan. 15, 2010

Re: [Pharo-project] [Vm-dev] use the vm -memory in an image ?

by John M McIntosh

The -memory parm is used by unix (or variations of) VM to set the upper memory size. For the OS-X carbon/cocoa VM it's in info.plist but can be overridden on cmd line. This has to be set BEFORE the VM runs since it determines how much memory to allocate either in a malloc block or via the operating system Virtual Memory subsystem. The value of 500/512 or so was set in the past before the VM was 32bit clean. People attempting to use 1GB sometimes would find their VM would crash as the image spanned the 2.GB memory boundary. However this problem was fixed a year or so ago. So you can either supply a -memory, alter info.plist if possible, or build your own VM and change the default value. On 2010-01-15, at 1:52 AM, Laval Jannik wrote: > > Hi, > > In some case I need to run my VM with more memory. > For now, I use the parameter "-memory" when I run the VM. > > Is it possible to define this value in the image ? > Then I can use it in a script. > > Cheers > > > --- > Jannik Laval > --- > -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 15, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by Laval Jannik

Hi, On Jan 15, 2010, at 10:57 , Mariano Martinez Peck wrote: > > > On Fri, Jan 15, 2010 at 10:51 AM, Laval Jannik <jannik.laval(a)inria.fr> wrote: > Hi, > > In some case I need to run my VM with more memory. > For now, I use the parameter "-memory" when I run the VM. > > Is it possible to define this value in the image ? > > > I think you can do something like: > > SmalltalkImage current > vmParameterAt: 5 put: 100000; > vmParameterAt: 6 put: 35000; > vmParameterAt: 24 put: 16 * 1024 * 1024; > vmParameterAt: 25 put: 8 * 1024 * 1024. > > > But...I am not sure how to know each parameter number what exactly is. Do you know where I can get that information? The method vmParameterAt: is documented, so : 5 allocations between GCs (read-write) 6 survivor count tenuring threshold (read-write) 24 memory threshold above which shrinking object memory (rw) 25 memory headroom when growing object memory (rw) Cheers, Jannik > > To see your current data I think you can do: > > SmalltalkImage current getVMParameters > > > Cheers > > Mariano > > Then I can use it in a script. > > Cheers > > > --- > Jannik Laval > --- > > > _______________________________________________ > 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. 15, 2010

[Pharo-project] [update 1.1] 11160

by StÃ©phane Ducasse

Service base removal (was reintroduced by 11159) Thanks alain for your flame fighting the dragons.

Jan. 15, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by Mariano Martinez Peck

On Fri, Jan 15, 2010 at 10:51 AM, Laval Jannik <jannik.laval(a)inria.fr>wrote: > Hi, > > In some case I need to run my VM with more memory. > For now, I use the parameter "-memory" when I run the VM. > > Is it possible to define this value in the image ? > I think you can do something like: SmalltalkImage current vmParameterAt: 5 put: 100000; vmParameterAt: 6 put: 35000; vmParameterAt: 24 put: 16 * 1024 * 1024; vmParameterAt: 25 put: 8 * 1024 * 1024. But...I am not sure how to know each parameter number what exactly is. Do you know where I can get that information? To see your current data I think you can do: SmalltalkImage current getVMParameters Cheers Mariano Then I can use it in a script. > > Cheers > > > --- > Jannik Laval > --- > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2010