March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Just found, i can compile this:

by Christophe Demarey

Why arguments should be read only? They are just temporary variables with an initial value. > 2014-03-18 15:45 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: > similiar to issue 12419 block arguments should be read only > > > 2014-03-18 15:21 GMT+01:00 Camille Teruel <camille.teruel(a)gmail.com>: > > Indeed, I can compile: > > C>>foo: arg > ^ arg := 3 > > And 'C new foo: 1' returns 3... > > > On 18 mars 2014, at 15:16, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > extent: newExtent > > > > vertical > > ifTrue: [ newExtent := self defaultWidth @ newExtent y ] > > ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. > > > > super extent: newExtent > > > > Can you verify it? Arguments should be not assignable. > > > > -- > > Best regards, > > Igor Stasenko. > > > >

March 18, 2014

Re: [Pharo-dev] Just found, i can compile this:

by ClÃ©ment Bera

Hello, For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. So 12419<https://pharo.fogbugz.com/default.asp?12419> is not a bug to me, it's a feature. For methods it is a bug, thanks for noticing. I will check. 2014-03-18 15:45 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: > similiar to issue 12419 <https://pharo.fogbugz.com/default.asp?12419> > block arguments should be read only > > > 2014-03-18 15:21 GMT+01:00 Camille Teruel <camille.teruel(a)gmail.com>: > > Indeed, I can compile: >> >> C>>foo: arg >> ^ arg := 3 >> >> And 'C new foo: 1' returns 3... >> >> >> On 18 mars 2014, at 15:16, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> > extent: newExtent >> > >> > vertical >> > ifTrue: [ newExtent := self defaultWidth @ newExtent y ] >> > ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. >> > >> > super extent: newExtent >> > >> > Can you verify it? Arguments should be not assignable. >> > >> > -- >> > Best regards, >> > Igor Stasenko. >> >> >> >

March 18, 2014

Re: [Pharo-dev] Just found, i can compile this:

by Nicolai Hess

similiar to issue 12419 <https://pharo.fogbugz.com/default.asp?12419> block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel <camille.teruel(a)gmail.com>: > Indeed, I can compile: > > C>>foo: arg > ^ arg := 3 > > And 'C new foo: 1' returns 3... > > > On 18 mars 2014, at 15:16, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > extent: newExtent > > > > vertical > > ifTrue: [ newExtent := self defaultWidth @ newExtent y ] > > ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. > > > > super extent: newExtent > > > > Can you verify it? Arguments should be not assignable. > > > > -- > > Best regards, > > Igor Stasenko. > > >

March 18, 2014

Re: [Pharo-dev] Just found, i can compile this:

by Camille Teruel

Indeed, I can compile: C>>foo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko <siguctua(a)gmail.com> wrote: > extent: newExtent > > vertical > ifTrue: [ newExtent := self defaultWidth @ newExtent y ] > ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. > > super extent: newExtent > > Can you verify it? Arguments should be not assignable. > > -- > Best regards, > Igor Stasenko.

March 18, 2014

Just found, i can compile this:

by Igor Stasenko

extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.

March 18, 2014

Re: [Pharo-dev] Looking for a project reloader tool

by Goubier Thierry

Le 18/03/2014 15:10, Ben Coman a Ã©crit : > Maybe the Configuration Browser could tag configurations to be loaded in > every new image. If the Startup scripts set a shared global package > cache directory [1], that information could be stored there. Hum, then this means that if you work on multiple projects in separate images, all of them will load the same configurations? > btw, How common is it to have a shared global package cache directory. > Should that be default? What would detract from that? I don't know but it seems that recent Pharo3 build have a tendency to create (or to share) a common cache. Or does that happens when you export settings? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

March 18, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Goubier Thierry

Le 17/03/2014 22:49, Max Leske a Ã©crit : > >> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > - annoy Esteban some more with libgit2 > - get other people to work on LibGit This is the project we should look at? http://smalltalkhub.com/#!/~StefanMarr/LibGit/commits > - move the repository to the FileSystem-Git-Dev team > - get fetch / pull working > - try to get the LibGit build working with Moose Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

March 18, 2014

Re: [Pharo-dev] Looking for a project reloader tool

by Ben Coman

March 18, 2014

Re: [Pharo-dev] pharo sound should be working

by J.F. Rick

I've tried the zeroconf script. It installs fine and it seems to work fine until I try to play sound. Then, it crashes. I get the following message in STD_OUT: sound_Start(default) sound_Start: snd_add_pcm_handler: Function not implemented ./pharo-ui: line 11: 5799 I/O possible "$DIR"/"pharo-vm/pharo" "$@" When I did "pharo -help", I get the following as sound drivers: vm-sound-null vm-sound-ALSA This is on Ubuntu 13.10. Cheers, Jeff On Mon, Mar 17, 2014 at 5:40 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > the ppa is not updated yet... this is a test version. > you have to install libasound2>i386 and libasound2-plugins:i386. > you get the vm with zeroconf: wget -O- get.pharo.org/vmLatest | bash > > Esteban > > On 17 Mar 2014, at 16:49, J.F. Rick <self(a)je77.com> wrote: > > What would I need to do to install it on Ubuntu? Could I just use the PPA? > If so, what are the commands? > > Cheers, > > Jeff > > > On Mon, Mar 17, 2014 at 3:45 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> can you check with the latest vm now? >> >> btw... you need to install: >> >> sudo apt-get install libasound2-plugins:i386 >> >> in order to prevent warnings. >> >> On 15 Mar 2014, at 00:03, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> 2014-03-14 21:43 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> Hi, >>> >>> so I committed some changes to allow soundplugin to work on the pharovm. >>> can you please download and test in your platforms? >>> >> >> Works on windows >> >> >> >>> >>> (remember, in linux you need libasound2 dependency installed) >>> >> >> it does not work on linux Ubuntu 12.04.2 LTS >> (I have installed libasound2). >> >> Why don't we include the pulse config again and build the vm-sound-pulse >> module as well? >> As I described it in the issue 12493, vm-sound-oss is buildable too. But >> current >> linux distribution don't provide the older OSS sound system. >> (it worked for me with ubuntu 10.04 but not with 12.04) >> >> >>> >>> cheers, >>> Esteban >>> >>> >> >> > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > > > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

March 18, 2014

Re: [Pharo-dev] Looking for a project reloader tool

by Martin Dias

On Tue, Mar 18, 2014 at 11:46 AM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > > On 18 Mar 2014, at 11:42, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > > yes but my projects are often not related. > > What I mean is: make a meta Metacello configuration, ConfigurationOfStef, > that loads everything you need by dependency. > > > Once, Mariano convinced me to do it this way and it was fine. Additionally, Metacello groups can be used to define multiple unrelated "working environments". Currently, I like to use .st startup scripts to define automatic small actions, and trigger Metacello for more complex actions. MartÃn

March 18, 2014