2016-02-16 9:52 GMT+01:00 kilon.alios <kilon.al...@gmail.com>: > So doing further research into Unreal , I have reached the conclusion that > the best way to integrate Pharo is make a compiler that takes Pharo code > and > compiles it to C++. >
even for C, there is no compiler that takes Pharo code and compiles it to C - binary code. what slang and vmmaker is doing, is more like a preprocessor, generating C - source code. Compiling C to code is done by an ordinary c-compiler, not smalltalk. > > I have barely scratch such area when I was playing around with Pharo AST > nodes. Any advice / ideas how to accomplish this ? > AST for pharo code is not used in any step generating vm code or FFI glue code AFAIK > > Currently my goal is to start super simple, with compiling small pharo code > fragments to C++ code and then much later on even introduce extensions to > the pharo language to accommodate for C++ features like templates , > pointers > (FFI probably already cover this) , static types etc. Obviously if I can > keep the pharo syntax intact would be the ideal option. > The attractiveness of NativeBoost was, that it can generate (written in smalltalk) glue code for interacting with C-libraries. Call functions, provide (C-Type)-arguments and process return values. "Mirror" C-Structures in the pharo image side and generate accessors for objects living in the heap memory. And the new FFI can do this (differently) too. But this is again only for C-libraries. If Unity does not provide a c-binding, it is really difficult to interact with it through a FF-interface. C++ code uses (theoretically every c++ runtime its own) different naming scheme for functions. You can not load and call c++ code the same way as for C. > > > > -- > View this message in context: > http://forum.world.st/Compiling-Pharo-to-C-tp4877775.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >
