- Pharo-dev - lists.pharo.org

Re: [Pharo-project] new pavel mini image :)

by Mariano Martinez Peck

PharoKernel are has to be run -headless. The only way (I think) to interact with it is sending scripts as parameters when starting the image from command line. Look http://code.google.com/p/pharo/wiki/PharoKernel Cheers Mariano 2010/2/27 GermÃ¡n Arduino <garduino(a)gmail.com> > Good news! > > May be that on Linux (Ubuntu 9.10) with vm pharo-vm-0.15.2f-linux don't > works? I get only a blank world were > nothing seems to respond. > > GermÃ¡n. > > > 2010/2/26 Marcus Denker <marcus.denker(a)inria.fr> > > >> On Feb 26, 2010, at 11:15 PM, Lukas Renggli wrote: >> >> > This is super cool! Exciting. >> > >> > The link doesn't seem to work though. Or at least I don't see where I >> > can download the image. >> > >> >> >> http://gforge.inria.fr/frs/download.php/26462/PharoKernel-1.1-11229-UNSTABL… >> >> > Lukas >> > >> > On 26 February 2010 20:42, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> >> Hi guys >> >> >> >> I do not know if you noticed by Pavel uploaded a new minimal image >> >> http://gforge.inria.fr/frs/shownotes.php?release_id=4921 >> >> >> >> This is really exciting. >> >> >> >> Stef >> >> >> >> _______________________________________________ >> >> Pharo-project mailing list >> >> Pharo-project(a)lists.gforge.inria.fr >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> > >> > >> > >> > -- >> > 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 >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> 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 >

Feb. 27, 2010

Re: [Pharo-project] new pavel mini image :)

by GermÃ¡n Arduino

Good news! May be that on Linux (Ubuntu 9.10) with vm pharo-vm-0.15.2f-linux don't works? I get only a blank world were nothing seems to respond. GermÃ¡n. 2010/2/26 Marcus Denker <marcus.denker(a)inria.fr> > > On Feb 26, 2010, at 11:15 PM, Lukas Renggli wrote: > > > This is super cool! Exciting. > > > > The link doesn't seem to work though. Or at least I don't see where I > > can download the image. > > > > > http://gforge.inria.fr/frs/download.php/26462/PharoKernel-1.1-11229-UNSTABL… > > > Lukas > > > > On 26 February 2010 20:42, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > >> Hi guys > >> > >> I do not know if you noticed by Pavel uploaded a new minimal image > >> http://gforge.inria.fr/frs/shownotes.php?release_id=4921 > >> > >> This is really exciting. > >> > >> Stef > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > > > > > -- > > 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 > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 27, 2010

Re: [Pharo-project] self halt

by Hilaire Fernandes

http://code.google.com/p/pharo/issues/detail?id=2088 StÃ©phane Ducasse a Ã©crit : > which update? > > On Feb 27, 2010, at 11:25 AM, Hilaire Fernandes wrote: > >> On a updated pharo 1.1 image, a "self halt" block the image. >> The debugger is raised but the UI is frozen. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 27, 2010

Re: [Pharo-project] Quasi-stateful traits?

by Stan Shepherd

Igor Stasenko wrote: > > > Traits can be reformulated to be purely a method source holders, not > holders of compiled methods. > (And btw, this is actually true, due to the latest changes in traits, > because of super sends issues and #methodClass) > OK, so that explains why they can currently be used as if they are stateful. > , we only need to push it a little further and get rid of > useless limitations. > > The point is, that all trait methods should _always_ be compiled in > the scope of the class to which it applied. > Because, for any variable name, which not declared explicitly in the > method's scope, we can't tell anything about it, > until we apply this method to the real class (See the Class>>bindingOf: ) > This means that, even if you having the trait method: > > foo > ^ Array new: 10 > > the binding of 'Array' variable may be different, depending on class > where its installed. > To check it, you can try following at home: > > Object subclass: #ZZZZ > instanceVariableNames: '' > classVariableNames: 'DD' > poolDictionaries: '' > category: 'ZZZZ' > > "add new pool variable" > ZZZZ classPool at: #Array put: 10. > > "now add the method" > array > ^ Array > > and now evaluate the following: > ZZZZ new array > > ------------- > But what makes > array > ^ Array > > method any better than > > array > ^ array := 10. > > in this regard? > > Nothing. So, why not drop the limitation, and instead of punishing > developer for use undeclared vars in trait methods, > punish him for use of undeclared variables, when he tries to apply the > trait to concrete class, where all such var names should obtain > meaning? > > Then, ultimately, what is the point in storing compiling methods in > Trait (not for classes, where it applied). We could just check the > syntax, but should not produce any CompiledMethod instances at all. > > What other problems i don't see here? > The merged OB/O2 case still passes a full system test, so I didn't run into any show-stoppers. Traits that work this way, supported by the tools, would appear to make them applicable to a lot more cases. ...Stan > On 27 February 2010 02:10, Stan Shepherd <stan.shepherd414(a)gmail.com> > wrote: >> >> >> Igor Stasenko wrote: >>> >>> One of the ways of introducing a stateful traits is changing the VM >>> object format. >>> >> Sounds like it could be very powerful. >> >> As it happens, in the fork healing example, it's the very statelessness >> of >> the traits that make it work so simply. By taking out the Â check for >> statefulness when the method is moved to a trait, the trait will quite >> happily address the several variables in its user classes. This then >> removes >> any need for accessors, helper classes for state, initialization, or >> other >> attempts to tame the beast. >> >> I wouldn't want to rely on it continuing to work in all conditions, but >> as a >> step in a refactoring it seems very handy. >> >> ..Stan >> -- >> View this message in context: >> http://n4.nabble.com/Quasi-stateful-traits-tp1571120p1571553.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 >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- View this message in context: http://n4.nabble.com/Quasi-stateful-traits-tp1571120p1571899.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 27, 2010

Re: [Pharo-project] self halt

by StÃ©phane Ducasse

which update? On Feb 27, 2010, at 11:25 AM, Hilaire Fernandes wrote: > On a updated pharo 1.1 image, a "self halt" block the image. > The debugger is raised but the UI is frozen. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 27, 2010

Re: [Pharo-project] Simple (but effective) Optimization of PackageOrganizer

by Serge Stinckwich

I see that a big earthquake hit Chile : http://www.alertnet.org/thenews/newsdesk/LDE61Q02O.htm I hope everything is ok with you. On Fri, Feb 26, 2010 at 6:58 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > issue #2085 > > Replace the method PackageOrganizer>>packageOfClass: aClass ifNone: > errorBlock by > -=-=-=-=-= > packageOfClass: aClass ifNone: errorBlock > Â Â Â Â | classCategory | > Â Â Â Â classCategory := aClass category. > Â Â Â Â packages at: classCategory ifPresent: [:v | ^ v]. > > Â Â Â Â (classCategory includes: $-) > Â Â Â Â Â Â Â Â ifTrue: [ packages at: (classCategory copyUpTo: $-) ifPresent: [:v | > ^ v] ]. > > Â Â Â Â ^ self packages detect: [:ea | ea includesClass: aClass] ifNone: > errorBlock > -=-=-=-=-= > > Before this enhancement: > [100 timesRepeat: [Object package]] timeToRun > => 141 > > After the fix: > => 2 > > Easy thing to do. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Feb. 27, 2010

Re: [Pharo-project] [update 1.1] #11234

by Marcus Denker

On Feb 27, 2010, at 12:11 PM, Marcus Denker wrote: > 11235 > -------- 11234 > > - Issue 2057: Clean Codeloader more... > - Issue 2029: Undeclared Variables > - Issue 1922: use #forceNewFileNamed:do: pattern > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 27, 2010

[Pharo-project] [update 1.1] #11235

by Marcus Denker

11235 --------- - Issue 1628: Error: There is no free space in this set!. - Enh Diff tool -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 27, 2010

[Pharo-project] [update 1.1] #11235

by Marcus Denker

11235 -------- - Issue 2057: Clean Codeloader more... - Issue 2029: Undeclared Variables - Issue 1922: use #forceNewFileNamed:do: pattern -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 27, 2010

[Pharo-project] self halt

by Hilaire Fernandes

On a updated pharo 1.1 image, a "self halt" block the image. The debugger is raised but the UI is frozen.

Feb. 27, 2010