November 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] CogVM crash code

by Jon Anderson

Hi all, I don't post to lists often, but I thought some of you might be interested in these few lines of code that crash the CogVM on both Linux and Windows. File-in the Smalltalk code below, then evaluate [nil crashCogVM]. The code uses [1-1] but it could use [1+1] or [56+98]. I put the code on nil, but that is not important either. I think the important thing is that the primitive (+ or -) is evaluated but the result is not assigned into any variable. Also important is that the code is put into a loop that I assume has been JIT optimized. The image I used is Pharo 1.4 one-click with latest update #14459. This code does not crash StackVM. Have fun! - Jon. !UndefinedObject methodsFor: 'crash' stamp: 'JonKAnderson 11/29/2012 17:26'! crashCogVM " Evaluate [ nil crashCogVM ]" | i | i := 20. 1 to: i do: [:d | 1-1 ] ! !

Nov. 30, 2012

Re: [Pharo-project] Vim Keys?

by Marcus Denker

On Nov 30, 2012, at 5:41 PM, âking <rkingdesk(a)sharpsaw.org> wrote: > On 11/30/2012 02:15 AM, Goubier Thierry wrote: >> It's underway. The infrastructure is moving to a better (unified) way of >> specifying and handling shortcuts, and then vi and vim-keys and emacs >> and others should become available. > > I have a radical question that I'd like to float. > > What about making vi keys not only possible, but the *default* for Pharo? > I am sure the Emacs user will be violently against it. Another thing is that I personally think that one of the things that Smalltalk did very early is to not have modes for editingâ¦ Are editing modes really something people want in 2012? (and no, I am not a vi user. I know one vi command and that is esc : q ! to get out of thereâ¦) Marcus

Nov. 30, 2012

Re: [Pharo-project] Vim Keys?

by âking

On 11/30/2012 02:15 AM, Goubier Thierry wrote: > It's underway. The infrastructure is moving to a better (unified) way of > specifying and handling shortcuts, and then vi and vim-keys and emacs > and others should become available. I have a radical question that I'd like to float. What about making vi keys not only possible, but the *default* for Pharo? They generally don't conflict with anything, because they're all "Namespaced" under sequences that you hit Escape for. This means you could continue to edit exactly as you do, but when you hit Esc you get some bonus functionality. And just because vi keys are the most hardcore interface ever of all time, that doesn't mean it has to be for neckbeards-only. We could make it so the text box has a status indicator, with help available and everything. Imagine a bar at the bottom that says, "Vi Command Mode", which can be clicked for a full help, then the rest of the bar has hints about common commands. It could even be adaptive, like learn to tell you commands that you haven't used much. The same bar could also say "Stop this crazy feature I don't like it". ââ

Nov. 30, 2012

[Pharo-project] [update 2.0] #20424

by Marcus Denker

20424 ----- Issue 7078: Do not hard code Browser in Hudson Build Tools http://code.google.com/p/pharo/issues/detail?id=7078 Issue 7073: Inconsistent System Browser selection http://code.google.com/p/pharo/issues/detail?id=7073 Issue 6928: Obsolete class after running all tests http://code.google.com/p/pharo/issues/detail?id=6928 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-MarcusDenker.993.diff http://ss3.gemstone.com/ss/Pharo20/Tests-MarcusDenker.485.diff http://ss3.gemstone.com/ss/Pharo20/System-Tools-MarcusDenker.91.diff http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-MarcusDenker.12.diff

Nov. 30, 2012

Re: [Pharo-project] Vim Keys?

by Chris Cunningham

There is a package (for an ancester of Pharo) that added VIM keys (and Emacs, apparently) to the editors at: http://www.squeaksource.com/SVI.html You may be able to load this in and it will work, or the code may have drifted quite a bit to the point where it just doesn't work anymore. I have not tried using it for years, myself. -Chris On Thu, Nov 29, 2012 at 11:52 AM, âking <rkingdesk(a)sharpsaw.org> wrote: > Hi all. I'm extremely new to Smalltalk, but I was wondering if there was > a way to make Pharo have vi-keys (or even better, vim-keys)? > > Thanks! > ââ > >

Nov. 30, 2012

Re: [Pharo-project] Indent code

by Sebastian Nozzi

Yep. Thank you! 2012/11/30 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: > it's actually cmd+shift+r/l > > Ben > > On Nov 30, 2012, at 4:04 PM, Sebastian Nozzi wrote: > >> On my Mac ctrl-alt l/r produced @ and Â® respectively (MBA 2011, german >> keyboard).

Nov. 30, 2012

Re: [Pharo-project] Indent code

by Benjamin

it's actually cmd+shift+r/l Ben On Nov 30, 2012, at 4:04 PM, Sebastian Nozzi wrote: > On my Mac ctrl-alt l/r produced @ and Â® respectively (MBA 2011, german > keyboard). > > 2012/11/30 Max Leske <maxleske(a)gmail.com>: >> on mac: ctrl+alt+r / l >> >> >> On 30.11.2012, at 12:49, Torsten Bergmann <astares(a)gmx.de> wrote: >> >>> When I select a few lines of text in Pharo 2.0 code >>> editor and hit TAB it is not indented as in >>> other IDE's. Instead it is deleted similar to >>> when one hits space key. >>> >>> Usually TAB in IDE code editors is used to >>> indent a selected block of text and SHIFT+TAB >>> is used for the reverse (outdent). >>> >>> Is this a bug or just handled differently? >>> >>> Thx >>> T. >>> >> >> >

Nov. 30, 2012

Re: [Pharo-project] Indent code

by Sebastian Nozzi

On my Mac ctrl-alt l/r produced @ and Â® respectively (MBA 2011, german keyboard). 2012/11/30 Max Leske <maxleske(a)gmail.com>: > on mac: ctrl+alt+r / l > > > On 30.11.2012, at 12:49, Torsten Bergmann <astares(a)gmx.de> wrote: > >> When I select a few lines of text in Pharo 2.0 code >> editor and hit TAB it is not indented as in >> other IDE's. Instead it is deleted similar to >> when one hits space key. >> >> Usually TAB in IDE code editors is used to >> indent a selected block of text and SHIFT+TAB >> is used for the reverse (outdent). >> >> Is this a bug or just handled differently? >> >> Thx >> T. >> > >

Nov. 30, 2012

Re: [Pharo-project] [ann] glamorous debugger (alpha)

by Damien Cassou

On Fri, Nov 30, 2012 at 3:12 PM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > It is really helpful to see what is going to be passed to a method or what > was its response. > yes, I should have added the following to the list of expressions I want to see a value for: self doSomething: (value at: 1) with: aStream next -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Nov. 30, 2012

[Pharo-project] About ArrayedCollection and at:/put:

by Igor Stasenko

It says: "I am an abstract collection of elements with a fixed range of integers (from 1 to n>=0) as external keys." now that leaves me clueless, why then it does not defines (introduces) a protocol: #at: and #at:put: at least as an abstract one , i.e. subclassResponsibility is it because they are already in Object protocol? And because subclasses (like Array) using default #at: implementation? I don't know, but i think Object should not have #at:/#at:put: protocol.. because: - it applicable only to variable subclasses - many classes have own implementation of it - the behavior behind this is to access a variable fields . while other classes use this protocol for higher abstractions (like dictionaries) so, to my thinking, Object should not define this protocol.. for this purpose we having #basicAt:/put: methods. btw, just an idea to clarify things even more, we could rename them to variableAt: [put:] (or any other name which properly tells that method provides an access to variable fields of object). -- Best regards, Igor Stasenko.

Nov. 30, 2012