July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Object>>doesNotUnderstand:

by Denis Kudriashov

> > I think that the bug is that you haven't modified the system to quit on an > UnhandledException. i.e. in a headless context control should never get > back to the doesNotUnderstand: method if the MessageNotUnderstood exception > is not caught. How should one continue after an unhandled error? > With my approach I have "null object message eating" behavior. And when any unhandled errors raised in system user will see nothing. Only log file will contain it. 2010/7/28 Eliot Miranda <eliot.miranda(a)gmail.com> > > > 2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> > > Hello, >> >> I found method doesNotUnderstand have very strange implementation >> >> Object>>doesNotUnderstand: aMessage >> | exception resumeValue | >> (exception := MessageNotUnderstood new) >> message: aMessage; >> receiver: self. >> resumeValue := exception signal. >> ^exception reachedDefaultHandler >> ifTrue: [aMessage sentTo: self] >> ifFalse: [resumeValue] >> >> When Error has no handlers #defaultAction is executed. For >> MessageNotUnderstood #defaultAction is UnhandledError signal. And for >> UnhandledError #defaultAction is opening debugger. >> If you change it to do nothing (^self) you get infinite loop on any >> MessageNotUnderstood signal. >> It is because "ifTrue" branch executed in doesNotUnderstood method and >> message resend to receiver. >> >> Why method implemented such way? Why it is differ from ProtoObject >> implementation. I think It's bug implementation. >> > > This is intentional. Martin's reply is one half of the issue, that you > want to be able to proceed after defining a method in the debugger. The > otehr half is that you want to be able to catch doesNotUnderstand: in an > exception handler and proceed with a result, e.g. > > [nil zork] > on: MessageNotUnderstood > do: [:ex| > ex message selector == #zork ifTrue: > [ex resume: #ok]. > ex pass] > > evaluates to #ok. > > >> >> I found this problem when I try implement stuff to turn off openning >> debugger on unhandled error (and write it to log) >> >> UnhandledError>>defaultAction >> "The current computation is terminated. The cause of the error should >> be logged or reported to the user. If the program is operating in an >> interactive debugging environment the computation should be suspended and >> the debugger activated." >> ^ToolSet debugError: exception. >> >> ToolSet class>>debugError: anError >> "Handle an otherwise unhandled error" >> self default ifNil:[ | ctx | >> Smalltalk >> logError: anError description >> inContext: (ctx := anError signalerContext) >> to: 'PharoDebug.log'. >> self inform: (anError description, String cr, ctx shortStack). >> ^anError return]. >> ^self default debugError: anError >> >> I just implement subclass of StandartToolSet with empty method >> #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled >> errors raise infinit loop and never return. >> >> I fix that by: >> >> MyToolSet>>debugError: anError >> anError class = MessageNotUnderstand ifTrue: [anError >> reachedDefaultHandler: true]. >> >> I think this is hack. But it is work. No errors show to user.And all work >> good. >> >> What do you think? >> > > I think that the bug is that you haven't modified the system to quit on an > UnhandledException. i.e. in a headless context control should never get > back to the doesNotUnderstand: method if the MessageNotUnderstood exception > is not caught. How should one continue after an unhandled error? > > HTH > Eliot > > >> Best regards, >> Denis >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Alexandre Bergel

> Good point... I've created it a critical tutorial task for it.... Else I forgot to say that your tutorial is very well done and quite useful. Very good job. I should do one for Mondrian... Alexandre > > Dale > > Alexandre Bergel wrote: >> Hi Dale, >> I tried your tutorial some times ago. This was not featured. Maybe this is something useful to have... >> Cheers, >> Alexandre >> On 27 Jul 2010, at 21:44, Dale Henrichs wrote: >>> Denis Kudriashov wrote: >>>> Hello >>>> Can I use configurations inner my configurations to set dependencies between packages. >>>> For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". >>>> But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. >>>> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? >>> Denis, >>> >>> You can refer to the XML config with the following statement in your baseline method define the project reference and the dependencies: >>> >>> ... >>> spec >>> project: 'XML Parser' with: [ >>> spec >>> className: 'ConfigurationOfXMLSupport'; >>> loads: #('Core'); >>> repository: 'http://www.squeaksource.com/MetacelloRepository' ]. >>> ... >>> spec package: 'myPackage' with: [ >>> spec requires: #('XML Parser'). >>> ... >>> >>> Then in your version method specify the particular version of the XML Parser that you want to use: >>> >>> ... >>> spec project: 'XML Parser' with: '1.0'. >>> .... >>> >>> Dale >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Dale Henrichs

Good point... I've created it a critical tutorial task for it.... Dale Alexandre Bergel wrote: > Hi Dale, > > I tried your tutorial some times ago. This was not featured. Maybe this is something useful to have... > > Cheers, > Alexandre > > > On 27 Jul 2010, at 21:44, Dale Henrichs wrote: > >> Denis Kudriashov wrote: >>> Hello >>> Can I use configurations inner my configurations to set dependencies between packages. >>> For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". >>> But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. >>> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? >> Denis, >> >> You can refer to the XML config with the following statement in your baseline method define the project reference and the dependencies: >> >> ... >> spec >> project: 'XML Parser' with: [ >> spec >> className: 'ConfigurationOfXMLSupport'; >> loads: #('Core'); >> repository: 'http://www.squeaksource.com/MetacelloRepository' ]. >> ... >> spec package: 'myPackage' with: [ >> spec requires: #('XML Parser'). >> ... >> >> Then in your version method specify the particular version of the XML Parser that you want to use: >> >> ... >> spec project: 'XML Parser' with: '1.0'. >> .... >> >> Dale >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

[Pharo-project] How do I enter Cyrillic letters in Pharo 1.1 / Seaside3.0rc images

by Stanislav Paskalev

Hello, Using the PBE 1.0 image, entering and displaying cyrillic characters works fine. However in Pharo 1.1 or the seaside image, all I get are question marks. I copied over the DejaVu fonts folder, selected "Install bitmap DejaVu fonts", but I'm still getting ???. What should I do so I can have them working ? Best regards, Stanislav Paskalev

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Eliot Miranda

2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> > Hello, > > I found method doesNotUnderstand have very strange implementation > > Object>>doesNotUnderstand: aMessage > | exception resumeValue | > (exception := MessageNotUnderstood new) > message: aMessage; > receiver: self. > resumeValue := exception signal. > ^exception reachedDefaultHandler > ifTrue: [aMessage sentTo: self] > ifFalse: [resumeValue] > > When Error has no handlers #defaultAction is executed. For > MessageNotUnderstood #defaultAction is UnhandledError signal. And for > UnhandledError #defaultAction is opening debugger. > If you change it to do nothing (^self) you get infinite loop on any > MessageNotUnderstood signal. > It is because "ifTrue" branch executed in doesNotUnderstood method and > message resend to receiver. > > Why method implemented such way? Why it is differ from ProtoObject > implementation. I think It's bug implementation. > This is intentional. Martin's reply is one half of the issue, that you want to be able to proceed after defining a method in the debugger. The otehr half is that you want to be able to catch doesNotUnderstand: in an exception handler and proceed with a result, e.g. [nil zork] on: MessageNotUnderstood do: [:ex| ex message selector == #zork ifTrue: [ex resume: #ok]. ex pass] evaluates to #ok. > > I found this problem when I try implement stuff to turn off openning > debugger on unhandled error (and write it to log) > > UnhandledError>>defaultAction > "The current computation is terminated. The cause of the error should > be logged or reported to the user. If the program is operating in an > interactive debugging environment the computation should be suspended and > the debugger activated." > ^ToolSet debugError: exception. > > ToolSet class>>debugError: anError > "Handle an otherwise unhandled error" > self default ifNil:[ | ctx | > Smalltalk > logError: anError description > inContext: (ctx := anError signalerContext) > to: 'PharoDebug.log'. > self inform: (anError description, String cr, ctx shortStack). > ^anError return]. > ^self default debugError: anError > > I just implement subclass of StandartToolSet with empty method > #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled > errors raise infinit loop and never return. > > I fix that by: > > MyToolSet>>debugError: anError > anError class = MessageNotUnderstand ifTrue: [anError > reachedDefaultHandler: true]. > > I think this is hack. But it is work. No errors show to user.And all work > good. > > What do you think? > I think that the bug is that you haven't modified the system to quit on an UnhandledException. i.e. in a headless context control should never get back to the doesNotUnderstand: method if the MessageNotUnderstood exception is not caught. How should one continue after an unhandled error? HTH Eliot > Best regards, > Denis > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Alexandre Bergel

Hi Dale, I tried your tutorial some times ago. This was not featured. Maybe this is something useful to have... Cheers, Alexandre On 27 Jul 2010, at 21:44, Dale Henrichs wrote: > Denis Kudriashov wrote: >> Hello >> Can I use configurations inner my configurations to set dependencies between packages. >> For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". >> But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. >> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? > Denis, > > You can refer to the XML config with the following statement in your baseline method define the project reference and the dependencies: > > ... > spec > project: 'XML Parser' with: [ > spec > className: 'ConfigurationOfXMLSupport'; > loads: #('Core'); > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > ... > spec package: 'myPackage' with: [ > spec requires: #('XML Parser'). > ... > > Then in your version method specify the particular version of the XML Parser that you want to use: > > ... > spec project: 'XML Parser' with: '1.0'. > .... > > Dale > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Martin McClure

On 07/27/2010 12:21 PM, Denis Kudriashov wrote: > Hello, > > I found method doesNotUnderstand have very strange implementation > [...] > > When Error has no handlers #defaultAction is executed. For > MessageNotUnderstood #defaultAction is UnhandledError signal. And for > UnhandledError #defaultAction is opening debugger. > If you change it to do nothing (^self) you get infinite loop on any > MessageNotUnderstood signal. > It is because "ifTrue" branch executed in doesNotUnderstood method and > message resend to receiver. > > Why method implemented such way? Why it is differ from ProtoObject > implementation. I think It's bug implementation. It's this way so that in development when you hit a MNU the debugger opens, you can define the missing method, hit proceed in the debugger, and it retries the send. It's not the best implementation for allowing the debugger to be turned off in production like you're doing. Regards, -Martin

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Denis Kudriashov

Thank you very much :)) 2010/7/27 Dale Henrichs <dhenrich(a)vmware.com> > Denis Kudriashov wrote: > >> Hello >> >> Can I use configurations inner my configurations to set dependencies >> between packages. >> >> For example, my application depends on XmlParser. In ConfigurationOfMyApp >> I need set "requires: 'XmlParser'". >> But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont >> want inspect ConfigurationOfXmlParser to see what packages I need load for >> XmlParser. >> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? >> >> >> >> Denis, > > You can refer to the XML config with the following statement in your > baseline method define the project reference and the dependencies: > > ... > spec > project: 'XML Parser' with: [ > spec > className: 'ConfigurationOfXMLSupport'; > loads: #('Core'); > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > ... > spec package: 'myPackage' with: [ > spec requires: #('XML Parser'). > ... > > Then in your version method specify the particular version of the XML > Parser that you want to use: > > ... > spec project: 'XML Parser' with: '1.0'. > .... > > Dale > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Dale Henrichs

Denis Kudriashov wrote: > Hello > > Can I use configurations inner my configurations to set dependencies between packages. > > For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". > But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. > Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? > > > Denis, You can refer to the XML config with the following statement in your baseline method define the project reference and the dependencies: ... spec project: 'XML Parser' with: [ spec className: 'ConfigurationOfXMLSupport'; loads: #('Core'); repository: 'http://www.squeaksource.com/MetacelloRepository' ]. ... spec package: 'myPackage' with: [ spec requires: #('XML Parser'). ... Then in your version method specify the particular version of the XML Parser that you want to use: ... spec project: 'XML Parser' with: '1.0'. .... Dale

July 27, 2010

[Pharo-project] Nested Configurations

by Denis Kudriashov

Hello Can I use configurations inner my configurations to set dependencies between packages. For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp?

July 27, 2010