I am looking at some interprocess communication with Pharo. VW has Opentalk, VASt has Sst (I think, haven’t looked in a while). Does anything similar exist for Pharo? Jerry Kott This message has been digitally signed. PGP Fingerprint: A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5 |
Administrator
|
I had the same quest. See the thread
http://forum.world.st/Smalltalk-to-Smalltalk-interface-td5099844.html#none Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
In reply to this post by Jerry Kott-3
Look at Seamless: https://github.com/pharo-ide/Seamless
Pretty powerfull - you are just using remote objects from another image like any other local object (proxying + serializing). pf > I am looking at some interprocess communication with Pharo. VW has Opentalk, VASt has Sst (I think, haven’t looked in a while). Does anything similar exist for Pharo? > > Jerry Kott > This message has been digitally signed. > PGP Fingerprint: > A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5 > > > |
In reply to this post by Jerry Kott-3
Hi Jerry,
We have worked on bridging Pharo with Python. It works remarkably well. Here is the website: https://objectprofile.github.io/PythonBridge/ We have also worked on a simple mechanism to distribute computation across multiple Pharo images. Here is the website: https://github.com/ObjectProfile/DMirror Cheers, Alexandre
|
In reply to this post by Jerry Kott-3
Nice! How does the DMirror relate to the ImageWorker? https://github.com/pharo-contributions/ImageWorker Norbert
|
I do not know what is ImageWorker, but DMirror is a simple and efficient way to distribute a computation on single CPU.
Alexandre
|
Sang did something similar a while ago too.
It allows an image to launch workers. One thing interesting is that they share virtual memory, so they can exchange data during the execution Noury
|
It would be nice to have one unified way for this *and* even think about shipping with that by default (so that we can use it e.g. for running tests.
Marcus
|
In reply to this post by Pharo Smalltalk Users mailing list
Subject was> Re: [Pharo-users] Anything on Pharo that would be like Opentalk on VW?) On Wed, 26 Jun 2019 at 02:45, Alexandre Bergel via Pharo-users <[hidden email]> wrote:
Hi Alexandre, How does usage of your Python bridge compare to Kilon's... ? cheers -ben |
No idea. But our bridge adequately manages errors crossing language boundaries and employ a set of command to enable promises. I am not sure sure whether Atlas was designed to do so. Alexandre |
I know a little Kilon’s bridge as I used it as backend for Python3Generator [1] in the beginning.
To my understanding , the difference is that Atlas is lower-level than PythonBridge. Basically, Atlas allows one to send python string and get back the returned value if it is a primitive type (int, float, str, etc). PythonBridge uses Python3Generator as DSL to build valid Python code. Atlas expects regular Pharo’s string. PythonBridge provides debugging facilities, Atlas does not to my knowledge. PythonBridge provides facilities to map Pharo classes to Python classes, Atlas does not. Cheers, Julien Links: --- Julien Delplanque Doctorant à l’Université de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq Numéro de téléphone: +333 59 35 86 40
|
Free forum by Nabble | Edit this page |