Camp Smalltalk project - transpiler infrastructure

I’m one of the principals for PharoJS which transpires from Smalltalk to Javascript

I’m the creator of PharoJVM which (is getting to) transpiling Smalltalk to JVM

I know there is new Pharo work on transpiling to C

There may be other transpires….

I think it would be good to work on a common transpiration structure that we can all extend. Ideally it should have pluggable targets, pluggable type inference, etc. but common parsing, management of classes to include, mocking of builtins, etc. I’d love for it to hook up with Live Types, too.

And just for the record. I wasn‘t talking more about NoSQL (mongo queries, AQL). Not sure the difference is big

Am 23.08.2019 um 19:47 schrieb David Mason <[hidden email]>:

I’ll probably be at the Stadtgarden around 14:30 Saturday and early Sunday and will start working on this whenever anyone else shows up and is interested in working on it. There seem to be at least 4 people besides me.

Known targets for transpilation include:
Javascript - PharoJS - working - dynamically typed, strange numeric stack - IWST papers describing mapping
JVM - PharoJVM - partial - statically typed, instance OO - IWST paper last year describing mapping
Illicium - ?working - statically typed, structs/unions - IWST paper this year
Python - dynamically typed, OO
SQL? - ? typed

So lots of variation to think about. Would be nice for all of the above to subclass a generic transpiler. See my earlier message for other considerations

../Dave
On 21.08.2019 at 18:18 David Mason <[hidden email]> wrote:

I’m one of the principals for PharoJS which transpires from Smalltalk to Javascript
I’m the creator of PharoJVM which (is getting to) transpiling Smalltalk to JVM
I know there is new Pharo work on transpiling to C
There may be other transpires….

I think it would be good to work on a common transpiration structure that we can all extend. Ideally it should have pluggable targets, pluggable type inference, etc. but common parsing, management of classes to include, mocking of builtins, etc. I’d love for it to hook up with Live Types, too.

../Dave

On Aug 23, 2019, 2:00 PM -0400, Norbert Hartl <[hidden email]>, wrote:

And just for the record. I wasn‘t talking more about NoSQL (mongo queries, AQL). Not sure the difference is big

Am 23.08.2019 um 19:47 schrieb David Mason <[hidden email]>:

I’ll probably be at the Stadtgarden around 14:30 Saturday and early Sunday and will start working on this whenever anyone else shows up and is interested in working on it. There seem to be at least 4 people besides me.

Known targets for transpilation include:
Javascript - PharoJS - working - dynamically typed, strange numeric stack - IWST papers describing mapping
JVM - PharoJVM - partial - statically typed, instance OO - IWST paper last year describing mapping
Illicium - ?working - statically typed, structs/unions - IWST paper this year
Python - dynamically typed, OO
SQL? - ? typed

So lots of variation to think about. Would be nice for all of the above to subclass a generic transpiler. See my earlier message for other considerations

../Dave
On 21.08.2019 at 18:18 David Mason <[hidden email]> wrote:

I’m one of the principals for PharoJS which transpires from Smalltalk to Javascript
I’m the creator of PharoJVM which (is getting to) transpiling Smalltalk to JVM
I know there is new Pharo work on transpiling to C
There may be other transpires….

I think it would be good to work on a common transpiration structure that we can all extend. Ideally it should have pluggable targets, pluggable type inference, etc. but common parsing, management of classes to include, mocking of builtins, etc. I’d love for it to hook up with Live Types, too.