May 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Artificial intelligence framework

by HernÃ¡n Morales Durand

Some old pieces: Neural Agents: http://dl.acm.org/citation.cfm?id=74892 (some source code in the paper itself) smallBrain http://ftp.sunet.se/pub/lang/smalltalk/st80_r41/smallBrain/ Cheers, HernÃ¡n El 04/05/2013 13:19, Ivan Hugo Guevara escribiÃ³: > Hi guys, how are you?. Do you know if there is a framework who simulates > neural networks?. > > Thanks in advance > > -- > Atte. IvÃ¡n Guevara

May 4, 2013

Artificial intelligence framework

by Ivan Hugo Guevara

Hi guys, how are you?. Do you know if there is a framework who simulates neural networks?. Thanks in advance -- Atte. IvÃ¡n Guevara

May 4, 2013

Re: [Pharo-users] Pharo 2.0 debugger strange behavior

by Marcus Denker

Hello, The problem is that the breakpoint mechanism is implemented extremely naivelyâ¦ (I once already suggested, no, urged, to remove it because it is just not good enough). Now in addition, the machinary for finding what to highlight is *extremely* complicated in the old compiler framework. The good news is that we have a new framework nearly ready in 3.0 that solves all of thisâ¦including *real* breakpointsâ¦ this is in active development and will be ready soon. But as it is a quite radical change, this is of course for 3.0 only. Now the problem is that nobody is willing to look at debugger highlighting related issue in the old framework. (there was a bug open for 4 yearsâ¦ with quite some brave people burning a lot of time without a solution). I want to spend all energy and time to finish the new oneâ¦ I just don't think that putting effort in the old Debugger is time well spend. Breakpoints there are not yet working at all in the new frameworkâ¦ but they will at soonish. I might even remove the old implementation, it's really just a bad hack and it was amazing that it worked at all. Marcus On May 4, 2013, at 5:34 PM, xavier MESSNER <xmessner(a)gmail.com> wrote: > Hi, > > Since Pharo 2.0 on Linux (20599) i have strange behavior when i'm trying to debug a method step by step. > > Step to reproduce : > > 1. Create a new Package 'TEST' > 2. Create a new subclass 'Test' > 3. Create a method 'Validation' > > Validation > |col| > col := OrderedCollection new. > col add: '1'. > col add: '2'. > col add: '3'. > > 4. Add a breakpoint on this method. > 5. Open a workspace > 6. Write on it : Test new validation. > 7. Alt-d to do it > > A debugger window appear. I choose 'debug' and then choose my method. I can see my code in the window. > Normally when you click on 'Over' you can go step by step through your instructions. > In 1.4 next instruction was highlighted, but not in 2.0 and 3.0. So you can't see what is done. > This feature in 1.4 save me a lot of time fighting bugs and learn smalltalk. > > Is this a bug ? someone has already seen that ? > > Regards, > > Xavier.

May 4, 2013

Pharo 2.0 debugger strange behavior

by xavier MESSNER

Hi, Since Pharo 2.0 on Linux (20599) i have strange behavior when i'm trying to debug a method step by step. Step to reproduce : 1. Create a new Package 'TEST' 2. Create a new subclass 'Test' 3. Create a method 'Validation' Validation |col| col := OrderedCollection new. col add: '1'. col add: '2'. col add: '3'. 4. Add a breakpoint on this method. 5. Open a workspace 6. Write on it : Test new validation. 7. Alt-d to do it A debugger window appear. I choose 'debug' and then choose my method. I can see my code in the window. Normally when you click on 'Over' you can go step by step through your instructions. In 1.4 next instruction was highlighted, but not in 2.0 and 3.0. So you can't see what is done. This feature in 1.4 save me a lot of time fighting bugs and learn smalltalk. Is this a bug ? someone has already seen that ? Regards, Xavier.

May 4, 2013