On 10/15/2015 11:57 AM, Robert Withers wrote:
On 10/15/2015 11:46 AM, Esteban Lorenzano wrote:
but well… in the mean time we learn and do steps. We will have a cool
FFI, don’t worry… sooner than later :D
I was thinking about ASMJIT and it's audience. You may attract a broader
audience with JVMJIT, including JNI. That would be something, then
support cross-calling between Pharo, Newspeak, Groovy, Scala and Java
plus dynamic jar loading. You'd need an army to pull that off though.
Please excuse the reply to the reply, but I was thinking about a JVMJIT
and cross-calling. The key to me, experientially, is to have the same
browser for all languages. We need a multi-language browser, a MLB.
Depending on the CompiledMethod selected, pick the right set of parsers:
compiler, pretty printer, code completion, type inferencer and the MLB's
method pane would be an editor for the language specified in the
compiled method.
Furthermore, to support cross-calling, when you are working is a
specific language, you can set that as the interaction language and the
browser will present interfaces from other languages in the language you
have selected, such that a cross-call is really just a native call to an
auto-generated wrapper around the other language.
Think of Cincom's Distributed Smalltalk talking Corba with their I3
(Implicit Invocation Interface):
http://www.cincomsmalltalk.com/main/documentation/VisualWorks/DSTAppDevGuide.pdf
I found this thread on Corba and Squeak:
http://squeak-dev.squeakfoundation.narkive.com/AbWTL8Kh/smalltalk-and-corba.
Bringing I3 support, into the browser would offer the foundations for
the MLB.
Any feedback is really appreciated!
Regards,
Robert
