[Gambas-user] Replacing the JIT component

[Jussi Lahtinen]

Well, ideally the user wont need to see the C translation. Only when there
is problems / discrepancy between compilation / execution of translated and
untranslated code.
So, some way to check the translation and compiler warnings from it, would
be nice.


Jussi

On Mon, May 7, 2018 at 2:13 PM, Benoît Minisini <g4mba5 at gmail.com> wrote:

> Le 06/05/2018 à 23:19, Jussi Lahtinen a écrit :
>
>> I think the #3 is excellent idea.
>> I think it makes the debugging much easier (I have no clue what current
>> JIT does to the code), if the C code is generated that point in mind.
>> Moreover I think it would very well fill the place of the missing/broken
>> feature. If you want to keep some of the code in native Gambas and need
>> high performance, then you can write two programs (one native and one
>> translated to C) and communicate between pipe, DBUS or whatever.
>>
>> No need to have function level compilation.
>>
>>
>> Jussi
>>
>>
>>
> The translated code will be stored inside the project executable, and you
> won't have an "untranslated" project and a "translated" project.
>
>
> Regards,
>
> --
> Benoît Minisini
>
> --------------------------------------------------
>
> This is the Gambas Mailing List:
> https://lists.gambas-basic.org/listinfo/user
>
> Search the list:
> https://lists.gambas-basic.org/cgi-bin/search.cgi
>
> Hosted by https://www.hostsharing.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20180507/3d1266fc/attachment-0001.html>