RE: Fwd: Octave JIT consultancy

[GoSim]

this is the interesting part:


> Run-time type analysis is based on the following prem-
> ise: If a line of M-code has been processed before, it is
> very likely that the variables have the same types and
> shapes that they had the last time the system saw this
> line. The first time that a line of code is executed, the
> system examines the variables and generates specific
> code for the data types and shapes that were found.
> Subsequent executions of the line can reuse this code
> as long as the system verifies that the variable types and
> sizes have not changed. Since the types rarely change,
> subsequent executions run as quickly as possible. If the
> types do change, the code is regenerated.

So it checks if the types changes. Easily done with a database of all
functions and all different input/output types. It seems to be clever enough
to not make this check on every line but just on lines where type changes is
possible. I prefer not allowing the user to change variable types and give
an error, but mathworks' solution is also nice.



--
Sent from: https://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html