Bytecode for transfer

Adapt transfer to use bytecode instead of tree walking. This task would be write a compiler and interpreter for Apertium transfer rules into the format of an an off-the-shelf bytecode engine (e.g. Java, v8, kjs, ...).

This page is to list ideas and their pros and cons.

Java bytecode

• There is a zillion of Open Source Java bytecode interpreters to choose from, most prominent Sun's own and http://kaffe.org.

• Theres is also a lot of more or less easy-to-use [Java bytecode generators].

• Considering that lttoolbox is on its way to being ported to Java. If Java bytecode was chosen this might eventually make Apertium run on J2ME devices (only the tagger is missing for a full system).

<jacobEo> spectie: jimregan I don't know, but I suppose that Java byte would run fastest, as there have been extremely 
  much work on optimize its speed, on different platforms....
<jacobEo> spectie: jimregan Also think in terms of some day get Apertium on a mobile phone.... then transfer in Java 
  bytecode would be the easiest thing. But if we don't at least also do Java bytecode, then we would have to write 
  a (non-Java) bytecode executor in J2ME.... pheh....
<jacobEo> spectie: jimregan Actually, if we get lttoolbox-java to work AND have Java bytecode for transfer, then we 
  instantly HAVE apertium running on phones! And also on Windows, many Unix variants, web pages, whatever can run Java bytecode.

Javascript bytecode

A Javascript engine.

External links

• Google v8: Embedder's documentation