- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 3.0] #30041

by ClÃ©ment Bera

Because I used it and there are some problems that might result in image freeze. Explicitely, problems with the debugger byte code to source code mapping or with new class compilation. And it was not planned to put Opal by default on Pharo because it cannot compile Slang whereas the old compiler can. But you can switch very easily (Settings >> OpalCompiler) 2013/4/16 Damien Cassou <damien.cassou(a)gmail.com> > On Tue, Apr 16, 2013 at 1:59 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > Opal is still not default compiler > > why not? Don't you think Opal will improve much faster if everyone uses it? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

April 16, 2013

Re: [Pharo-project] How to browse a selected method in code viewer

by kilon

Ah ok its in there, i did not see it. Why is it not in top ? its seems very important tool to be in a sub menu. Also I have another issue it does not work always, if I select method and choose browser it does nothing but reopens the right menu, the weird thing is that senders and implementors work fine but also reopen the right click menu. In 90% of the cases does not work. Anyone else having the same issues on Ubuntu 12.10 mad64 ? I dont know if this is a AthensTutorial bug , seems some people have it with even do it. I tried Altbrowser from the configurations tool , changed to it and still get same behavior. -- View this message in context: http://forum.world.st/How-to-browse-a-selected-method-in-code-viewer-tp4681… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 16, 2013

Re: [Pharo-project] [update 3.0] #30041

by Marcus Denker

On Apr 16, 2013, at 2:12 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Tue, Apr 16, 2013 at 1:59 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Opal is still not default compiler > > why not? Don't you think Opal will improve much faster if everyone uses it? > There are some errors in the bcoffset->IR->AST mapping that lead to problems when using the debugger. Marcus

April 16, 2013

Re: [Pharo-project] How to browse a selected method in code viewer

by Damien Cassou

On Tue, Apr 16, 2013 at 2:11 PM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > What I mean is that while browsing a method, if I found a message and > wanted to browse its code i could highlight > with my mouse (select the text) right click and select "browse" from the > menu. As Esteban says, it is under the "Extended search" submenu. You can also press Alt+m to do the same. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 16, 2013

Re: [Pharo-project] Metacello configuration conventions

by Christophe Demarey

As a general purpose reflexion on dependencies conventions, I would say: If you are in development mode, it makes sense to rely on latest versions of dependencies (bleeding edge) to be able to detect integration problems as soon as possible. If you are in a release mode, you should ensure that your code can run at least on fixed dependencies versions (at the best, specify a range of versions you can use with possibly no upper limit if your dependencies ensure backward compatibility). You need reproducible loading of your tool/lib. in my opinion, you shouldn't use #stable for release version as the only thing it ensure (if well tested) is that you will not have a broken version of the dependency. The stable version of your dependency will evolve and then the configuration of your release too. At a time, your version will not be usable at all because of that. so I would specify a dependency with a versionString for release versions of your lib/tool. It ensures a minimum version. Regards, Christophe. Le 16 avr. 2013 Ã 11:02, Frank Shearar a Ã©crit : > On 16 April 2013 09:53, Stephan Eggermont <stephan(a)stack.nl> wrote: >> Hi, >> >> While working with Diego on some configurations, we noticed two different styles >> of describing the latest non-baseline versions. >> >> In one, the versionString version of a dependency is used. >> That is a defensive strategy, where you want to specify the exact version that >> will be loaded (and has been tested). >> >> In the other the #stable version is used. That is an optimistic strategy. >> This is much less brittle (but might suddenly not work anymore). >> >> Seaside uses defensive/mixed, while Magritte uses optimistic >> >> Based on what criteria should I choose which one to use (in a Pharo context)? > > I'd argue that since you're declaring that a certain set of versions > of packages work together, you should _always_ use explicit versions. > The "optimistic" strategy leaves you vulnerable to third parties > making seemingly innocuous changes that break your code. (I've been > bitten by this, by making such an apparently innocuous change.) > > frank > >> Stephan & Diego >

April 16, 2013

Re: [Pharo-project] [regression reporter]regression occurred

by Goubier Thierry

Le 16/04/2013 14:11, Marcus Denker a Ã©crit : > > On Apr 16, 2013, at 2:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> oops... those are a lot of regressions :) > > This should not happen: This means that somehow Opal is taken as the compiler. > (The tests are not compatible between the two, we are going through them one by > one, either porting or fixingâ¦ but it takes while). > > If they fail this mean that the wrong compiler is used when running the tests. Who was asking if it wasn't a good idea to use Opal by default ? Markus, look, plenty of failed tests to help you progress :) Thierry >> >> On Apr 16, 2013, at 2:06 PM, no-reply(a)ci.inria.fr wrote: >> >>> https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… >>> >>> 71 regressions found. >>> CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation >>> CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames >>> CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto >>> CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto >>> CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto >>> CompilerTests.CompilerExceptionsTest.testAmbiguousSelector >>> CompilerTests.CompilerExceptionsTest.testUndeclaredVariable >>> CompilerTests.CompilerExceptionsTest.testUndefinedVariable >>> CompilerTests.CompilerExceptionsTest.testUnknownSelector >>> CompilerTests.CompilerExceptionsTest.testUnusedVariable >>> CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp >>> CompilerTests.CompilerNotifyingTest.testAlltogether >>> CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf >>> CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend >>> CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix >>> CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement >>> CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray >>> CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock >>> CompilerTests.CompilerNotifyingTest.testInvalidRadix >>> CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing >>> ... >>> >> >> > > > > -- 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

April 16, 2013

Re: [Pharo-project] Understanding Athens

by Damien Cassou

On Tue, Apr 16, 2013 at 2:20 PM, kilon <thekilon(a)yahoo.co.uk> wrote: > Should I assume it works for Fedora but its not available for Ubuntu ? yum is not meant to be used on Ubuntu system. For Ubuntu, just do: $ sudo apt-get install libcairo2:i386 -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 16, 2013

Re: [Pharo-project] How to browse a selected method in code viewer

by Esteban Lorenzano

what Gisela is doing is smart suggestions: not the same, a lot better :) The function Dimitris is asking for (browse a method imp. accesing with mouse) is already there (it never left), just in a different submenu Esteban On Apr 16, 2013, at 2:21 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Le 16/04/2013 14:11, dimitris chloupis a Ã©crit : >> When I was using squeak a feature I used alot was the ability to browse >> a selected method. What I mean is that while browsing a method, if I >> found a message and >> wanted to browse its code i could highlight >> with my mouse (select the text) right click and select "browse" from the >> menu. This way >> I did not need to search for the method manually by mouse or use a >> search field. I am using >> Pharo 2.0 and I cannot find any such feature in the system browser , am >> I missing something ? > > Gisela is currently implementing / has implemented that for Nautilus. > > If you want to experiment that, load the ConfigurationOfAltBrowser and try AltBrowser; you don't even need to select, the browser will extend and show you the selector (and then you can choose implementors). There are a few other commands implemented that way (access/rename instance variables). > > 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 >

April 16, 2013

Re: [Pharo-project] How to browse a selected method in code viewer

by Goubier Thierry

Le 16/04/2013 14:11, dimitris chloupis a Ã©crit : > When I was using squeak a feature I used alot was the ability to browse > a selected method. What I mean is that while browsing a method, if I > found a message and > wanted to browse its code i could highlight > with my mouse (select the text) right click and select "browse" from the > menu. This way > I did not need to search for the method manually by mouse or use a > search field. I am using > Pharo 2.0 and I cannot find any such feature in the system browser , am > I missing something ? Gisela is currently implementing / has implemented that for Nautilus. If you want to experiment that, load the ConfigurationOfAltBrowser and try AltBrowser; you don't even need to select, the browser will extend and show you the selector (and then you can choose implementors). There are a few other commands implemented that way (access/rename instance variables). 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

April 16, 2013

Re: [Pharo-project] [update 3.0] #30041

by Esteban Lorenzano

because there are still some emerging bugs that prevents its use :) On Apr 16, 2013, at 2:11 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Tue, Apr 16, 2013 at 1:59 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Opal is still not default compiler > > why not? Don't you think Opal will improve much faster if everyone uses it? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

April 16, 2013