February 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

by Blondeau Vincent

I donât think so: Put a halt here: â¦ifTrue: [self halt. aMessage sentTo: self]â¦ 1. Open a playground 2. Do: Object new toto You should have a debugger that pops. Donât close it. 3. Go in Nautilus, implement toto on Object 4. Click on proceed in the debugger. You should have a Halt instead. And if you click on proceed again, it should execute the toto method. So it is used, and I frequently use it. Cheers, Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Denis Kudriashov EnvoyÃ© : jeudi 25 fÃ©vrier 2016 18:06 Ã : Discusses Development of Pharo Objet : Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why? Maybe in past it was used to create methods in debugger on the fly. But now it is not. I just check it. I removed recursion logic and methods creation continue working in debugger. Maybe we should remove this strange behaviour 2016-02-25 17:56 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com<mailto:dionisiydk@gmail.com>>: Hi. Does anybody know why #doesNotUnderstand: is implemented with recursion at the end? doesNotUnderstand: aMessage | exception resumeValue | (exception := MessageNotUnderstood new) message: aMessage; receiver: self. resumeValue := exception signal. ^exception reachedDefaultHandler ifTrue: [aMessage sentTo: self] ifFalse: [resumeValue]. Best regards, Denis !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Feb. 25, 2016

Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

by Nicolai Hess

Am 25.02.2016 6:30 nachm. schrieb "Aliaksei Syrel" <alex.syrel(a)gmail.com>: > > Just a guess, maybe to allow method adding from debugger and then ability to continue execution? > > Cheers, > Alex > > On Thu, Feb 25, 2016 at 5:56 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> Hi. >> >> Does anybody know why #doesNotUnderstand: is implemented with recursion at the end? >> >>> doesNotUnderstand: aMessage >>> | exception resumeValue | >>> (exception := MessageNotUnderstood new) >>> message: aMessage; >>> receiver: self. >>> resumeValue := exception signal. >>> ^exception reachedDefaultHandler >>> ifTrue: [aMessage sentTo: self] >>> ifFalse: [resumeValue]. >> There is a difference between sentTo: and sendTo: >> >> Best regards, >> Denis > >

Feb. 25, 2016

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3632. These include 64-bit VMs whose Smalltalk execution and FFI are functional. However, their SocketPlugin is more than somewhat broken. Executing the SocketPlugin tests results in a hard lockup, at least on Mac OS X. This is my next focus for 64-bits. ------------------------------------------------------------------------ CogVM binaries as per VMMaker.oscog-eem.1700/r3632 General: Fix serious bug in jitted perform: primitive. Thanks to Stephane Rollandin for finding and to Levente Uzoni for diagnosing the bug. If the argument count is one greater than the max number of register arguments (2 in Spur, hence perform:with:with:) then the code to remove the receiver and arguments from the stack neglects to remove the receiver and selector. Spur: Fix special selector arithmetic and comparison in the 64-bit Cogit. My original code for genJumpNotSmallIntegersIn:andScratchReg: merely jumped if the tags differed, hence not jumping if both arguments were SmallFloat64s (or both Characters). The new code requires an additional scratch register; hence add genJumpNotSmallIntegersIn:andScratch:scratch:. Fix bug in markAndTraceWeaklingsFrom:. Fields of weaklings may be immediate so must use followOopField:ofObject: not followObjField:ofObject:. Fix https://pharo.fogbugz.com/f/cases/17536/VM-Crash-when-adding-an-iVar-to-a-s… . When weaklings (and when ephemerons) are scan-marked forwarders must be coped with. 64-bit VMs: Fix a bug in printHex: for 64-bits (faulty arithmetic). ThreadedFFIPlugin: Fix the remaining 64-bit issues in the ThreadedFFIPlugin. The X64SysVFFIPlugin now passes the test suite. Hence include the FFI plugin in 64-bit VMs. Make the SqueakFFIPrims plugin internal in the Mac pharo builds. Mac VMs: Have the Mac OS X build install Localizable.strings. Add versions for Newspeak, Pharo and Squeak. Rename the key to SelectImagePanePrompt. Temporarily disable the Serial plugin in the Pharo Mac VM until we can track down the relevant platforms/iOS support for the Pharo extensions. Fix argument access on the iOS platform (Mac OS VMs). _,,,^..^,,,_ best, Eliot

Feb. 25, 2016

Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

by Eliot Miranda

Hi Denis, On Thu, Feb 25, 2016 at 8:56 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > Does anybody know why #doesNotUnderstand: is implemented with recursion at > the end? > > doesNotUnderstand: aMessage > | exception resumeValue | > (exception := MessageNotUnderstood new) > message: aMessage; > receiver: self. > resumeValue := exception signal. > * ^exception reachedDefaultHandler* > * ifTrue: [aMessage sentTo: self]* > ifFalse: [resumeValue]. > > It's so that when a doesNotUnderstand: occurs and one implements the method in the debugger one can proceed. The sentTo: at the end will now invoke the newly defined method and one can continue programming. Best regards, > Denis > _,,,^..^,,,_ best, Eliot

Feb. 25, 2016

Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

by Aliaksei Syrel

Just a guess, maybe to allow method adding from debugger and then ability to continue execution? Cheers, Alex On Thu, Feb 25, 2016 at 5:56 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > Does anybody know why #doesNotUnderstand: is implemented with recursion at > the end? > > doesNotUnderstand: aMessage > | exception resumeValue | > (exception := MessageNotUnderstood new) > message: aMessage; > receiver: self. > resumeValue := exception signal. > * ^exception reachedDefaultHandler* > * ifTrue: [aMessage sentTo: self]* > ifFalse: [resumeValue]. > > > Best regards, > Denis >

Feb. 25, 2016

Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

by Blondeau Vincent

Hi, Because when you are receiving a DNU, you have the possibility to implement the method before resuming the exception. If you choose to implement the method, the message is sent again to the newly created method and the execution restarts. Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Denis Kudriashov EnvoyÃ© : jeudi 25 fÃ©vrier 2016 17:56 Ã : Discusses Development of Pharo Objet : [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why? Hi. Does anybody know why #doesNotUnderstand: is implemented with recursion at the end? doesNotUnderstand: aMessage | exception resumeValue | (exception := MessageNotUnderstood new) message: aMessage; receiver: self. resumeValue := exception signal. ^exception reachedDefaultHandler ifTrue: [aMessage sentTo: self] ifFalse: [resumeValue]. Best regards, Denis !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Feb. 25, 2016

Re: [Pharo-dev] Recursion inside #doesNotUnderstand: method. Why?

by Denis Kudriashov

Maybe in past it was used to create methods in debugger on the fly. But now it is not. I just check it. I removed recursion logic and methods creation continue working in debugger. Maybe we should remove this strange behaviour 2016-02-25 17:56 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi. > > Does anybody know why #doesNotUnderstand: is implemented with recursion at > the end? > > doesNotUnderstand: aMessage > | exception resumeValue | > (exception := MessageNotUnderstood new) > message: aMessage; > receiver: self. > resumeValue := exception signal. > * ^exception reachedDefaultHandler* > * ifTrue: [aMessage sentTo: self]* > ifFalse: [resumeValue]. > > > Best regards, > Denis >

Feb. 25, 2016

Recursion inside #doesNotUnderstand: method. Why?

by Denis Kudriashov

Hi. Does anybody know why #doesNotUnderstand: is implemented with recursion at the end? doesNotUnderstand: aMessage | exception resumeValue | (exception := MessageNotUnderstood new) message: aMessage; receiver: self. resumeValue := exception signal. * ^exception reachedDefaultHandler* * ifTrue: [aMessage sentTo: self]* ifFalse: [resumeValue]. Best regards, Denis

Feb. 25, 2016

Re: [Pharo-dev] debugger versus primitive 19 "simulation guard"

by Denis Kudriashov

I revert this case in 17698 <https://pharo.fogbugz.com/f/cases/17698/Debugger-step-through-proxies-is-no…> 2016-02-25 12:24 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > Trying to debug step two times into... > [ 'a' ] newProcess > ...hangs the image. > > It works okay with... > Pharo5.0 update: #50495 > NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: > 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14904 > Unix built on Apr 2 2015 00:51:53 Compiler: 4.6.3 > > but not with... > Pharo5.0 update: #50496 > CoInterpreter VMMaker.oscog-eem.1630 uuid: > 2ed025ea-f400-4440-8e8b-5aa46d06c9ab Jan 14 2016 > 21ec004cce7d26010c18d357c805a0e1a4ffe376 Date: 2016-01-14 11:42:33 > +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #498 > Unix built on Jan 14 2016 11:50:34 Compiler: 4.6.3 > > > btw, the same case on Squeak-4.6-All-In-one and Squeak-5-All-In-One > both produce "Code simulation error." > > Is it maybe related to... "another endless debugger loop" > https://pharo.fogbugz.com/default.asp?16877 > > cheers -ben > >

Feb. 25, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50613 Home: https://github.com/pharo-project/pharo-core

Feb. 25, 2016