- Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to resurrect an unrepsonsive image?

by Henrik Sperre Johansen

On 09.12.2011 16:59, Schwab,Wilhelm K wrote: > I would be very curious about what happens if you replace the socket-related mutual exclusion semaphores with mutexes. For the semaphore in question here, there is no recursion going on in any of the critical sections. So the answer to that would be absolutely nothing. Cheers, Henry

Dec. 9, 2011

Re: [Pharo-project] GUI Testing Library

by Sean P. DeNigris

Sean P. DeNigris wrote > > I will open an issue Issue 5077: UI simulation from BDDExtensions project http://code.google.com/p/pharo/issues/detail?id=5077 -- View this message in context: http://forum.world.st/GUI-Testing-Library-tp4097866p4177726.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 9, 2011

Re: [Pharo-project] RB AST Rewriter to eliminate/consoliate temporary variables?

by Lukas Renggli

>>> But in this simple example, I could remove t2 and use t1 instead. >> >> No, "o1 foo", "o2 bar: t1", "o3 bar: t1" could have side-effects that >> influence what "o1 foo" returns. No tool on the world (without >> additional knowledge) can safely replace "t2" with "t1". > > It is about the slot, not about the value. This is a perfectly legal transformation: > > | t1 | > t1 := o1 foo. > o2 bar: t1. > o3 bar: t1. > > t1 := o1 foo. > o2 bar: t1. > o3 bar: t1. > > That is the same what register allocators do. t1, as a slot, is not going to be read anymore, thus, the slot can be used to hold another temporary value. Luckily Smalltalk is not a register machine. Even if your example looks perfectly linear, the order in which the statements are executed is pretty much unpredictable (think of exceptions, continuations, reflection, ...). > Well, anyway, I just hope that I can work around the frame size limitations when I encounter them in real code. The NewCompiler had a visitor that would overflow excess literals into arrays. You could theoretically do the same for excess temps. Lukas -- Lukas Renggli www.lukas-renggli.ch

Dec. 9, 2011

Re: [Pharo-project] GUI Testing Library

by Tudor Girba

Hi, I think the best would be to add it externally from a configuration. So, I created one: Gofer new squeaksource: 'BDDExtensions'; package: 'ConfigurationOfBDDExtensions'; load. (Smalltalk at: #ConfigurationOfBDDExtensions) loadDevelopment At the moment it only has a 1.0-baseline with BDDExtensions and Keymapping-Shortcuts. Cheers, Doru On 9 Dec 2011, at 17:13, Sean P. DeNigris wrote: > > Tudor Girba-2 wrote >> >> Btw, I think these should get in the Pharo distribution because they >> are just too valuable. >> > > I will open an issue and submit a slice. Do you have any > suggestions/requests while I'm there? I think the only basic thing missing > is middle-click, which will be easy to add. Right now we have: > * send a string of keystrokes > * send a single keystroke, with modifiers if desired > * left click > * right click > * choose item from menu > > Except for the tests, there's only extension methods, which I'll > recategorize. The ones I have questions about are: > * TestCase - I know SUnit is an external project. Is ours forked? i.e. can I > add methods to it? > * Keymapping - simulating modifier keys requires Keymapping-Shortcuts. What > would be best? > > Sean > > -- > View this message in context: http://forum.world.st/GUI-Testing-Library-tp4097866p4177181.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- www.tudorgirba.com "Live like you mean it."

Dec. 9, 2011

Re: [Pharo-project] RB AST Rewriter to eliminate/consoliate temporary variables?

by Stefan Marr

Hi: On 09 Dec 2011, at 18:10, Lukas Renggli wrote: >> I basically want to be able to automatically reduce the number of temps for the following example to one: >> >> | t1 t2 | >> t1 := o1 foo. >> o2 bar: t1. >> o3 bar: t1. >> >> t2 := o1 foo. >> o2 bar: t2. >> o3 bar: t2. >> >> Of course it is slightly more complex than that, because the usage of the temps is not just in a sequence, but can be also in blocks, or nested expressions. >> >> But in this simple example, I could remove t2 and use t1 instead. > > No, "o1 foo", "o2 bar: t1", "o3 bar: t1" could have side-effects that > influence what "o1 foo" returns. No tool on the world (without > additional knowledge) can safely replace "t2" with "t1". It is about the slot, not about the value. This is a perfectly legal transformation: | t1 | t1 := o1 foo. o2 bar: t1. o3 bar: t1. t1 := o1 foo. o2 bar: t1. o3 bar: t1. That is the same what register allocators do. t1, as a slot, is not going to be read anymore, thus, the slot can be used to hold another temporary value. Well, anyway, I just hope that I can work around the frame size limitations when I encounter them in real code. Thanks Stefan > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Dec. 9, 2011

Re: [Pharo-project] RB AST Rewriter to eliminate/consoliate temporary variables?

by Lukas Renggli

> I basically want to be able to automatically reduce the number of temps for the following example to one: > > | t1 t2 | > t1 := o1 foo. > o2 bar: t1. > o3 bar: t1. > > t2 := o1 foo. > o2 bar: t2. > o3 bar: t2. > > Of course it is slightly more complex than that, because the usage of the temps is not just in a sequence, but can be also in blocks, or nested expressions. > > But in this simple example, I could remove t2 and use t1 instead. No, "o1 foo", "o2 bar: t1", "o3 bar: t1" could have side-effects that influence what "o1 foo" returns. No tool on the world (without additional knowledge) can safely replace "t2" with "t1". Lukas -- Lukas Renggli www.lukas-renggli.ch

Dec. 9, 2011

Re: [Pharo-project] RB AST Rewriter to eliminate/consoliate temporary variables?

by Stefan Marr

Hi Lukas: On 09 Dec 2011, at 16:54, Lukas Renggli wrote: > Hi Stefan, > > I think there is a lint rule that does that: TempNotRead ... I don't > have an image at hand, but I can check tonight if you haven't found it > until then. Thanks, I checked the lint rules, but well, while there are some rules which provide related analysis, what I was looking for is slightly more complex. I basically want to be able to automatically reduce the number of temps for the following example to one: | t1 t2 | t1 := o1 foo. o2 bar: t1. o3 bar: t1. t2 := o1 foo. o2 bar: t2. o3 bar: t2. Of course it is slightly more complex than that, because the usage of the temps is not just in a sequence, but can be also in blocks, or nested expressions. But in this simple example, I could remove t2 and use t1 instead. Well, for the moment, I just removed the offending test from the system, but since my benchmarks do not run yet, I fear that I might run into the problem with real code, too. Best regards Stefan > > Lukas > > On 9 December 2011 16:29, Stefan Marr <pharo(a)stefan-marr.de> wrote: >> Hi all, >> Hi Lukas: >> >> Do you know if anyone ever implemented a rewriter for the RB AST that reduces the amount of temporary variables if possible? >> >> I have a naive rewriting step that creates too many temps, but some of them are not strictly necessary. >> >> However, currently, I run into 'Cannot compile -- stack including temps is too deep' which is, well, ehm, not so nice. >> >> In case anyone has something in that direction, I would be interested. >> >> Thanks >> Stefan >> >> -- >> Stefan Marr >> Software Languages Lab >> Vrije Universiteit Brussel >> Pleinlaan 2 / B-1050 Brussels / Belgium >> http://soft.vub.ac.be/~smarr >> Phone: +32 2 629 2974 >> Fax: +32 2 629 3525 >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Dec. 9, 2011

Re: [Pharo-project] GUI Testing Library

by Sean P. DeNigris

Tudor Girba-2 wrote > > Btw, I think these should get in the Pharo distribution because they > are just too valuable. > I will open an issue and submit a slice. Do you have any suggestions/requests while I'm there? I think the only basic thing missing is middle-click, which will be easy to add. Right now we have: * send a string of keystrokes * send a single keystroke, with modifiers if desired * left click * right click * choose item from menu Except for the tests, there's only extension methods, which I'll recategorize. The ones I have questions about are: * TestCase - I know SUnit is an external project. Is ours forked? i.e. can I add methods to it? * Keymapping - simulating modifier keys requires Keymapping-Shortcuts. What would be best? Sean -- View this message in context: http://forum.world.st/GUI-Testing-Library-tp4097866p4177181.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 9, 2011

Re: [Pharo-project] Exception Handling in the Moose Distribution Image

by Marcus Denker

On Dec 9, 2011, at 4:25 PM, Mircea Filip Lungu wrote: > Hi guys, > > This is a bug report I got from one of my students and replicated by myself: > > In the Moose 4.6 image downloaded from moosetechnology.org, if I > execute the following code > > | c | > c := Collection new. > c add: 1. > > the image seems to freeze, although what I would expect is that > SubclassResponsibility > exception to be raised. This has been observed on Windows and Mac. > > Do you know about this? > This has been fixed in 1.4 last week... as a workaround, I think filing in this should work: -- Marcus Denker -- http://marcusdenker.de

Dec. 9, 2011

Re: [Pharo-project] How to resurrect an unrepsonsive image?

by Schwab,Wilhelm K

I would be very curious about what happens if you replace the socket-related mutual exclusion semaphores with mutexes. Are you also using background image saves for persistence? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Sean P. DeNigris [sean(a)clipperadams.com] Sent: Friday, December 09, 2011 10:51 AM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] How to resurrect an unrepsonsive image? Norbert Hartl wrote > > Trying to recover the image was not important for me but for pharo. I just > liked to participate in solving a problem that is hard to debug. > Right on, Norbert!! Thank you for doing that. This already happened to me twice and it is a difficult and important problem for us. Sean -- View this message in context: http://forum.world.st/How-to-resurrect-an-unrepsonsive-image-tp4168518p4177… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 9, 2011