Re: [Pharo-project] Compiler does not barks anymore for unknown selectors?
On Apr 19, 2012, at 11:05 PM, Mariano Martinez Peck wrote:
Hi guys. Previously, in Pharo 1.3, when compiling a method that has message sent to an unknown selector, the compiler used to bark and open a popup suggesting other similar messages or to choose the one you originally wanted. Now it does not bark nor opens a popup. Instead it direcly puts what I said. Is that expected?
Is your selector really unknown? -- Marcus Denker -- http://marcusdenker.de
I noticed the same. I didn't say anything because I prefer this behavior :) On Apr 20, 2012, at 8:13 AM, Marcus Denker wrote:
On Apr 19, 2012, at 11:05 PM, Mariano Martinez Peck wrote:
Hi guys. Previously, in Pharo 1.3, when compiling a method that has message sent to an unknown selector, the compiler used to bark and open a popup suggesting other similar messages or to choose the one you originally wanted. Now it does not bark nor opens a popup. Instead it direcly puts what I said. Is that expected?
Is your selector really unknown? -- Marcus Denker -- http://marcusdenker.de
participants (2)
-
Esteban Lorenzano -
Marcus Denker