Hi Kilon, the way your are explaining it, it seems you are trying to build a Smalltalk-like syntax in C++ via templates?
It could make moving a software architecture from Smalltalk to C++ significantly easier (and open maybe some opportunities). Thierry 2016-02-16 11:00 GMT+01:00 kilon.alios <kilon.al...@gmail.com>: > Ok first my apology to people because I see that many have misunderstood my > motivation. > > So let me be crystal clear. > > *This IS NOT an effort to make Pharo "super cool". "Look mom Pharo compiles > to C++ magically, it runs blazzing fast, it can use C++ libraries with zero > efforts" and similar none sense.* > > Unfortunately I cannot use Pharo as a scripting language that would be > awesome but I afraid not possible. Compiling Unreal as a set of dlls is > somewhat possible but the problem is that iOS does not allow dlls, iOS > support is super crucial for me so that goes out of the window. Embeding > Pharo in Unreal is no go either since pharo does not support this. > > I am not looking into bringing Pharo features to C++. For example I dont > care about dynamic types because Unreal depends a lot on templates which > are > very dynamic, I dont care about Pharo GC because unreal has its own GC, I > dont care about Pharo reflection because Unreal also gives C++ reflection > features, I dont even care about Pharo live coding because Unreal also > allow > to hot reload on the fly when you recompile C++ code. > > WARNING !!! I am not saying that coding C++ in Unreal is better , more > dynamic or more live than Pharo. Pharo is awesome. > > So my thinking is like this, I cannot avoid C++. So since I cannot avoid it > then maybe I could try to make it more enjoyable by making it move closer > to > pharo syntax. > > That means my implementation will do a lot of nasty compromises, meaning > manual memory managment, disallow dynamic types (though later on with the > help of templates maybe I can make it more dynamic) , have to include > headers etc. So in general write C++ code using something that is close to > pharo syntax. My goal is not an ideal solution but a practical solution > something that is relative simple to make for a single developer. > > It wont be a tool you guys will be using because it will be too tied to > Unreal anyway and it will contain the nasty parts of C++. The idea will be > similar to what Cython is for python, start prototyping in pure python with > all the great features it has, then when code works as you expect start > inserting static types, manual memory management etc to turn it to C++. > > I hope now I am much more clear what I aiming for > > > > > > > > > > > > > -- > View this message in context: > http://forum.world.st/Compiling-Pharo-to-C-tp4877775p4877821.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >
