----- Original Message -----
> From: Alex Vong <alexvong1...@gmail.com>
> To: Jordi Gutiérrez Hermoso <jord...@octave.org>
> Cc: Ricardo Wurmus <rek...@elephly.net>; guix-devel@gnu.org; Leo Famulari
> <l...@famulari.name>; help-oct...@gnu.org; Mike Miller <mtmil...@octave.org>
> Sent: Saturday, August 13, 2016 3:12 PM
> Subject: Re: JIT compiling
>
> Jordi Gutiérrez Hermoso <jord...@octave.org> writes:
>
>> On Thu, 2016-08-11 at 23:27 +0800, Alex Vong wrote:
>>> Finally, some unrelated stuff, I hope octave would have a byte code
>>> interpreter soon. I would suggest to write it in rpython, it seems
>>> to be the easiest way to have jit these days.
>>
>> That is a faraway pipe dream. Can you help?
>>
> I think I will be too un-experienced to help, but I am interested in
> it. I've always dreamt octave having good anoymous and nested function
> support. I think the first step is to prase octave correctly. Is there a
> reference on it other than the libinterp code itself?
>
>> - Jordi G. H.
>
> Cheers,
>
> Alex
>
> _______________________________________________
> Help-octave mailing list
> help-oct...@gnu.org
> https://lists.gnu.org/mailman/listinfo/help-octave
>
"I've always dreamt octave having good anoymous and nested function
support" - then switch to Perl -> PDL (http://pdl.perl.org/) or OCaml (if you
want type strictness and near "C" performance).
...
When Julia language was first discussed here, I suggested to write an Octave ->
Julia translator, but I think it will NEVER be done for ideological (fanatic
support of false/fake GPL freedom) reasons.
The rationale was to get the best of the two worlds - speed of Julia and
packages available for Octave - in addition to what already exists for Julia.
--Sergei.
