- Pharo-dev - lists.pharo.org

Re: [Pharo-project] NB Capabilities

by Jimmie Houchin

The COM API is deprecated and no longer supported. Only the C++ API is what is available for use from Pharo. On 11/8/2012 11:31 PM, Igor Stasenko wrote: > On 8 November 2012 23:25, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >> On a second look at the API's documentation, the DLL is C++ not C. I don't >> know, but that might have been evident by the requirement of implementing >> interfaces. > well, with C++ it is a bit worse than C: because C++ compilers use > name mangling for the function names. > Means that, if you will look for exported function 'abc()', you will > probably find it under different name, like > abc@nby_xrt How does one go about discovering these names? > apart from that, once you figure the exact correct name, you can go > and call that function. > > Things is a bit different if the exported function is a member of class. > > So, what i can say.. you can try and see if it rolls (or rocks).. and > if it not, then the best option would be to implement own wrapper > library (but this time in C). And then use that library from pharo. Ok, then this is the tricky part because I have a lot of C++ classes which are interfaces to be implemented and instances of those classes to be passed into other instances of other classes in the DLL. An example from the documentation. ''' An instance of the class implementing |IO2GSessionStatus| interface must be subscribed to the session object before calling IO2GSession <IO2GSession.html>::login <IO2GSession.login.html> method. It is accomplished by calling |IO2GSession| <IO2GSession.html>::|subscribeSessionStatus| <IO2GSession.subscribeSessionStatus.html> method. For example, ... ''' As it stands my options are to learn Clojure (which I am already in progress of doing) in order to access the API via Java. Or to learn C/C++ and NB to access the API from Pharo. I like Pharo, but I am not sure at this point, if that is the easiest or best option. I am concerned about learning just enough C++ to shoot myself in the foot. I am also concerned that the C/C++ route will take much more significant learning than Clojure. Going with Clojure does not automatically rule out Pharo. Depending on how much I like or don't like dealing with Clojure/Java and whether or not I would want to implement the rest of my application there. I could also choose to use it to serve the API via http/websockets to a Pharo application. Thanks for your help. Jimmie

Nov. 9, 2012

Re: [Pharo-project] Don't ever ever halt in #startUp:

by Jan Vrany

Better to replace symbol #halt with #yourself in the method litarray. Doing it uncoditionally in all compiled methods should not hurt. Easier and safer :-) Jan On 09/11/12 14:31, Henrik Sperre Johansen wrote: > On 09.11.2012 13:36, Sebastian Nozzi wrote: >> 2012/11/9 Igor Stasenko <siguctua(a)gmail.com>: >>> My recipe is: >>> - simply find an offending compiled method >>> - replace its first bytecode to "returnself" >> How do you do this? >> > One could potentially build a tool to do it :) > (with the caveat that one would need to be intimate with the > image/object format) > > - Open a "dead" image file. > - Find offsets for start of object space and symbol table (in the image > header?) > - Search for startUp/startUp:/halt in Symbol table, and record their > object header adresses > - Subtract the object space start start from these, and you'd have the > oop's of these Symbols. > - Scan the image for startUp(:) oops, check if it's the selector of a > CompiledMethod instance, and that halt is one of it's literals. > - If so, replace the first byte in the CM's bytecodes with that of > returnself. > > If you want to do so manually, better get your Neo-goggles on, or be > Igor :P > > Cheers, > Henry >

Nov. 9, 2012

Re: [Pharo-project] Don't ever ever halt in #startUp:

by Henrik Sperre Johansen

On 09.11.2012 13:36, Sebastian Nozzi wrote: > 2012/11/9 Igor Stasenko <siguctua(a)gmail.com>: >> My recipe is: >> - simply find an offending compiled method >> - replace its first bytecode to "returnself" > How do you do this? > One could potentially build a tool to do it :) (with the caveat that one would need to be intimate with the image/object format) - Open a "dead" image file. - Find offsets for start of object space and symbol table (in the image header?) - Search for startUp/startUp:/halt in Symbol table, and record their object header adresses - Subtract the object space start start from these, and you'd have the oop's of these Symbols. - Scan the image for startUp(:) oops, check if it's the selector of a CompiledMethod instance, and that halt is one of it's literals. - If so, replace the first byte in the CM's bytecodes with that of returnself. If you want to do so manually, better get your Neo-goggles on, or be Igor :P Cheers, Henry

Nov. 9, 2012

Re: [Pharo-project] [Jenkins] about Pharo ci infrastructure...

by Marcus Denker

Hi, Good idea! I will forward it to the team working on the ci platform. Marcus On Nov 9, 2012, at 10:49 AM, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > Since it is still in beta testing maybe there is still time to consider some > theme-ing to change the default Jenkins look to something nicer (since it > serves more than just Pharo maybe INRIA branded?) ... and yes I know there > are more important things to be done but I wanted to suggest it anyway ;) > > http://www.amazon.com/Jenkins-Continuous-Integration-Cookbook-Alan/dp/18495… > More info on how to: "Skin Jenkins to your corporate look and feel" > > > > -- > View this message in context: http://forum.world.st/Jenkins-about-Pharo-ci-infrastructure-tp4654364p46546… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Marcus Denker -- http://marcusdenker.de

Nov. 9, 2012

[Pharo-project] [update 2.0] #20387

by Esteban Lorenzano

20387 ----- Issue 2178: Reverse the logic and avoid a copy in DeflateStream http://code.google.com/p/pharo/issues/detail?id=2178 Issue 6760: Traits don't get repackaged http://code.google.com/p/pharo/issues/detail?id=6760 Issue 6937: RGMonticelloTest in unsuitable package http://code.google.com/p/pharo/issues/detail?id=6937 Issue 6941: Extend Startup SafetyNet for Halt http://code.google.com/p/pharo/issues/detail?id=6941 Diff information: http://ss3.gemstone.com/ss/Pharo20/Traits-EstebanLorenzano.443.diff http://ss3.gemstone.com/ss/Pharo20/System-Support-EstebanLorenzano.731.diff http://ss3.gemstone.com/ss/Pharo20/Ring-Tests-Monticello-EstebanLorenzano.2… http://ss3.gemstone.com/ss/Pharo20/Ring-Tests-Kernel-EstebanLorenzano.38.di… http://ss3.gemstone.com/ss/Pharo20/Compression-EstebanLorenzano.116.diff

Nov. 9, 2012

[Pharo-project] Pharo Kernel Tests failures

by Pavel Krivanek

Hi, I created a summary of tests that fail on Pharo Kernel. Currently 44 tests are failing as result of about 16 issues. https://docs.google.com/spreadsheet/ccc?key=0AjSsmZhqtUTedHBid1R4U0hFOVBWME… Keep in mind that Pharo Kernel has not complete tests coverage because some tests packages need reorganization. On the other hand the amount of loaded tests is not small. It has 7250 tests while full Pharo has 9659 tests. Help in this area is welcome ;-) We (at least I) want to have green tests for the final 2.0 release. Cheers, -- Pavel

Nov. 9, 2012

Re: [Pharo-project] [Jenkins] about Pharo ci infrastructure...

by Geert Claes

ci.inria.fr <https://ci.inria.fr> looks very nice by the way :) -- View this message in context: http://forum.world.st/Jenkins-about-Pharo-ci-infrastructure-tp4654364p46546… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 9, 2012

Re: [Pharo-project] [Jenkins] about Pharo ci infrastructure...

by Geert Claes

Since it is still in beta testing maybe there is still time to consider some theme-ing to change the default Jenkins look to something nicer (since it serves more than just Pharo maybe INRIA branded?) ... and yes I know there are more important things to be done but I wanted to suggest it anyway ;) http://www.amazon.com/Jenkins-Continuous-Integration-Cookbook-Alan/dp/18495… More info on how to: "Skin Jenkins to your corporate look and feel" -- View this message in context: http://forum.world.st/Jenkins-about-Pharo-ci-infrastructure-tp4654364p46546… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 9, 2012

Re: [Pharo-project] NB Capabilities

by drush66

Fernando olivero-2 wrote > Hi, i wanted to give my opinion on this, since i've encountered some of > the > problems you mention. > > Sometimes to benefit from the simplicity of Smalltalk while coexisting > with > other tools, we must cope with low level technology "glue code". > > NB made it easy to do so, compared to Alien,FFI, writing plugins in C. > When > i first started with Squeak and the Pharo1.0, it was a real pain > interfacing with external libraries, THANKS Igor! > > Still someones needs to do it, hence why a lot of people of > this community spent loads of time coding this "extra work" to be able to > do their "real work". > > I wouldn't say that you need to be extremely bright to built a wrapper > library using NB, once you know what api you want to call, and the type of > arguments. > > There's plenty of examples out there, and Igor always responds with tough > questions! > > Give a try! maybe its easier than you think. > > Fernando just to clarify, I was not referring to interfacing to c library which is rather well covered by NB, but to COM. ----- http://www.cloud208.com/ -- View this message in context: http://forum.world.st/NB-Capabilities-tp4654570p4654631.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 9, 2012

Re: [Pharo-project] Don't ever ever halt in #startUp:

by Sebastian Nozzi

2012/11/9 Igor Stasenko <siguctua(a)gmail.com>: > My recipe is: > - simply find an offending compiled method > - replace its first bytecode to "returnself" How do you do this?

Nov. 9, 2012