- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] VM for Athens Graphics

by StÃ©phane Ducasse

Igor this is not the point. People do not understand that code can be represented as text :) If I save assembly in XML is it XML or assembly. I think that if you have a dll whose contents does not change then it is ok. Stef

Oct. 25, 2013

Re: [Pharo-dev] VM for Athens Graphics

by StÃ©phane Ducasse

> > Ok I was not aware you were thinking about that. So this is good to have this path in my radar. > > Yes, this is actually what we discussed recently with Esteban about possible alternatives and > low-hanging fruits :) I like these ones :) > >> Concerning ARM: >> - Damien Pollet works on ARM assembler for ASMJit. >> as soon as it working, we can try doing something with it. >> >> But in addition, what i would like to do is to move more towards platform-neutral FFI implementation, >> using low-level assembler DSL which is platform neutral. There's a work started on it >> as part of Mate project, but it is yet far from finished. > > I would love that. > Now I guess that I'm correct to say that even with it the fact that it would generate assembly on the fly > would make it a no go for iPad and friends. > > I thought that esteban and you thought about generating the "assembly once for all for Ipda and putting it in file" > so that we do not have the "assembly generation" problem? > > that's a big question, whether such idea fits into apple technicians/politicans heads or not. > Do you think we have enough time/resources to waste on implementing such mechanism > only to discover later that Apple says 'over my dead body'? > The point is that generating code, saving it to file, and then loading that file as DLL, > is largely a hack. > You either allowed to run your own generated code or not.. because from security perspective, > the fact that you first stored it into file and then load it back doesn't changes a tiny bit. > From design perspective, it is crutch, which don't really buys anything (why on earth, anyone would want to deal with files > and OS, if he could just run code which already in memory?). >

Oct. 25, 2013

Re: [Pharo-dev] API docs?

by projectVALIS

perfect! this is enough to get me going -- thanks!!! -- View this message in context: http://forum.world.st/API-docs-tp4716945p4717010.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 25, 2013

Re: [Pharo-dev] API docs?

by Torsten Bergmann

projectVALIS wrote: > I'm wondering if there are online API docs like there are for Java (here's a > link <http://docs.oracle.com/javase/7/docs/api/> for all you non-Java > types). I've already got a copy of 'Pharo by Example' and 'A Guide to Work > with Squeak Morph Classes', but neither are what I'm looking for. Also, the > 'swiki' doesn't have a comprehensive list. An up-to-date reference of the > morphs and classes available in a stock Pharo image would be immensely > helpful. Does one exist? Sure - one is available in the PharoOnlineHelp. In a fresh Pharo 2.0 or Pharo 3.0 image just open Tools -> ConfigurationBrowser Then select "PharoOnlineHelp" from the list and install it. After loading there is a panel where you can start the local webserver. If you are on Windows then click on "Browse" afterwards to open the webbrowser, otherwise (Mac, Linux) point your browser to http://localhost:8080 In the toolbar click on "API". A screenshot is available here: http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20121129/a… JavaDoc is "dead" documentation since it is just generated from the classes and easily outdated. The Pharo API docu is served right out of the image and is therefore always up to date. It is based on class and method comments that you also have within the environment. Independent from that I would rather use the Smalltalk browser than this kind of docu - it gives you much more control. Have fun T.

Oct. 25, 2013

Re: [Pharo-dev] Unwind error during termination

by Levente Uzonyi

On Fri, 25 Oct 2013, Nicolas Cellier wrote: > Hard to debug this kind of code :( > This is reproducible on Squeak wiht on:do:, so on:fork: bizareness apart, this is another flaw in exception handling, along with wrong handler for nested exception (testHandlerFromAction below), unless it's > an avatar. > > Still, I do not see how you get the errorSubscriptBound:... > In Squeak that would mean that you sent #handleSignal: to a not isHandlerContext ContextPart... > I never saw this, but if Eliot says so... > > > > ExceptionTests>>testHandlerFromAction > Â Â Â "A test ensuring that nested exceptions work as expected." > > Â Â Â | result | > Â Â Â result := [ > Â Â Â Â Â Â [ > Â Â Â Â Â Â Â Â Â [self error: 'trigger error'] on: ZeroDivide do: [ :ex | 'inner' ] > Â Â Â Â Â Â ] on: Error do: [ :ex | 3 / 0 ] > Â Â Â ] on: ZeroDivide do: [ :ex | 'outer' ]. > Â Â Â self assert: 'outer' equals: result description: 'Incorrect handler'. I had an attempt to fix it, but it's incomplete, and other issues popped up: http://lists.squeakfoundation.org/pipermail/squeak-dev/2012-August/165364.h… Levente > > > > 2013/10/24 Igor Stasenko <siguctua(a)gmail.com> > > ok, it seems i found how to reproduce the situation with following: > > [Â [ 1/0 ] ensure: [ nil foo ] ] on: Error fork: [ :ex | 1halt ] > > you will get halt, and if you close the debugger , it will throw unwind error. > (while instead it should throw DNU) > > > -- > Best regards, > Igor Stasenko. > > > >

Oct. 25, 2013

Re: [Pharo-dev] Unwind error during termination

by Igor Stasenko

On 25 October 2013 01:28, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > The author of the test is Andreas Raab, but I'm not sure who found it > (excavating mailing list is hard work) > > and this test is missing in pharo, so thanks anyways :) i can't imagine what can't go wrong is such basic stuff is broken. so we should fix it first, and then see if on:fork: needs some extra handling. > 2013/10/25 Igor Stasenko <siguctua(a)gmail.com> > >> >> >> >> On 25 October 2013 00:26, Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> Hard to debug this kind of code :( >>> This is reproducible on Squeak wiht on:do:, so on:fork: bizareness >>> apart, this is another flaw in exception handling, along with wrong handler >>> for nested exception (testHandlerFromAction below), unless it's an avatar. >>> >>> Still, I do not see how you get the errorSubscriptBound:... >>> In Squeak that would mean that you sent #handleSignal: to a not >>> isHandlerContext ContextPart... >>> I never saw this, but if Eliot says so... >>> >>> >>> >>> ExceptionTests>>testHandlerFromAction >>> "A test ensuring that nested exceptions work as expected." >>> >>> | result | >>> result := [ >>> [ >>> [self error: 'trigger error'] on: ZeroDivide do: [ :ex | >>> 'inner' ] >>> ] on: Error do: [ :ex | 3 / 0 ] >>> ] on: ZeroDivide do: [ :ex | 'outer' ]. >>> self assert: 'outer' equals: result description: 'Incorrect handler'. >>> >>> good find :) >> >> https://pharo.fogbugz.com/f/cases/11996/Wrong-exception-handler-problem >> >> >>> >>> >>> 2013/10/24 Igor Stasenko <siguctua(a)gmail.com> >>> >>>> >>>> ok, it seems i found how to reproduce the situation with following: >>>> >>>> [ [ 1/0 ] ensure: [ nil foo ] ] on: Error fork: [ :ex | 1halt ] >>>> >>>> you will get halt, and if you close the debugger , it will throw unwind >>>> error. >>>> (while instead it should throw DNU) >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

Oct. 24, 2013

Re: [Pharo-dev] Unwind error during termination

by Nicolas Cellier

The author of the test is Andreas Raab, but I'm not sure who found it (excavating mailing list is hard work) 2013/10/25 Igor Stasenko <siguctua(a)gmail.com> > > > > On 25 October 2013 00:26, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> Hard to debug this kind of code :( >> This is reproducible on Squeak wiht on:do:, so on:fork: bizareness apart, >> this is another flaw in exception handling, along with wrong handler for >> nested exception (testHandlerFromAction below), unless it's an avatar. >> >> Still, I do not see how you get the errorSubscriptBound:... >> In Squeak that would mean that you sent #handleSignal: to a not >> isHandlerContext ContextPart... >> I never saw this, but if Eliot says so... >> >> >> >> ExceptionTests>>testHandlerFromAction >> "A test ensuring that nested exceptions work as expected." >> >> | result | >> result := [ >> [ >> [self error: 'trigger error'] on: ZeroDivide do: [ :ex | >> 'inner' ] >> ] on: Error do: [ :ex | 3 / 0 ] >> ] on: ZeroDivide do: [ :ex | 'outer' ]. >> self assert: 'outer' equals: result description: 'Incorrect handler'. >> >> good find :) > > https://pharo.fogbugz.com/f/cases/11996/Wrong-exception-handler-problem > > >> >> >> 2013/10/24 Igor Stasenko <siguctua(a)gmail.com> >> >>> >>> ok, it seems i found how to reproduce the situation with following: >>> >>> [ [ 1/0 ] ensure: [ nil foo ] ] on: Error fork: [ :ex | 1halt ] >>> >>> you will get halt, and if you close the debugger , it will throw unwind >>> error. >>> (while instead it should throw DNU) >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> > > > -- > Best regards, > Igor Stasenko. >

Oct. 24, 2013

Re: [Pharo-dev] Unwind error during termination

by Igor Stasenko

On 25 October 2013 00:26, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > Hard to debug this kind of code :( > This is reproducible on Squeak wiht on:do:, so on:fork: bizareness apart, > this is another flaw in exception handling, along with wrong handler for > nested exception (testHandlerFromAction below), unless it's an avatar. > > Still, I do not see how you get the errorSubscriptBound:... > In Squeak that would mean that you sent #handleSignal: to a not > isHandlerContext ContextPart... > I never saw this, but if Eliot says so... > > > > ExceptionTests>>testHandlerFromAction > "A test ensuring that nested exceptions work as expected." > > | result | > result := [ > [ > [self error: 'trigger error'] on: ZeroDivide do: [ :ex | > 'inner' ] > ] on: Error do: [ :ex | 3 / 0 ] > ] on: ZeroDivide do: [ :ex | 'outer' ]. > self assert: 'outer' equals: result description: 'Incorrect handler'. > > good find :) https://pharo.fogbugz.com/f/cases/11996/Wrong-exception-handler-problem > > > 2013/10/24 Igor Stasenko <siguctua(a)gmail.com> > >> >> ok, it seems i found how to reproduce the situation with following: >> >> [ [ 1/0 ] ensure: [ nil foo ] ] on: Error fork: [ :ex | 1halt ] >> >> you will get halt, and if you close the debugger , it will throw unwind >> error. >> (while instead it should throw DNU) >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

Oct. 24, 2013

API docs?

by projectVALIS

Hi all, I'm wondering if there are online API docs like there are for Java (here's a link <http://docs.oracle.com/javase/7/docs/api/> for all you non-Java types). I've already got a copy of 'Pharo by Example' and 'A Guide to Work with Squeak Morph Classes', but neither are what I'm looking for. Also, the 'swiki' doesn't have a comprehensive list. An up-to-date reference of the morphs and classes available in a stock Pharo image would be immensely helpful. Does one exist? -- View this message in context: http://forum.world.st/API-docs-tp4716945.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 24, 2013

Re: [Pharo-dev] Unwind error during termination

by Nicolas Cellier

Hard to debug this kind of code :( This is reproducible on Squeak wiht on:do:, so on:fork: bizareness apart, this is another flaw in exception handling, along with wrong handler for nested exception (testHandlerFromAction below), unless it's an avatar. Still, I do not see how you get the errorSubscriptBound:... In Squeak that would mean that you sent #handleSignal: to a not isHandlerContext ContextPart... I never saw this, but if Eliot says so... ExceptionTests>>testHandlerFromAction "A test ensuring that nested exceptions work as expected." | result | result := [ [ [self error: 'trigger error'] on: ZeroDivide do: [ :ex | 'inner' ] ] on: Error do: [ :ex | 3 / 0 ] ] on: ZeroDivide do: [ :ex | 'outer' ]. self assert: 'outer' equals: result description: 'Incorrect handler'. 2013/10/24 Igor Stasenko <siguctua(a)gmail.com> > > ok, it seems i found how to reproduce the situation with following: > > [ [ 1/0 ] ensure: [ nil foo ] ] on: Error fork: [ :ex | 1halt ] > > you will get halt, and if you close the debugger , it will throw unwind > error. > (while instead it should throw DNU) > > > -- > Best regards, > Igor Stasenko. >

Oct. 24, 2013