| … | |
… | |
| 26 | the stack faster, and the opcodes themselves have a bit less overhead. |
26 | the stack faster, and the opcodes themselves have a bit less overhead. |
| 27 | |
27 | |
| 28 | Faster is in the early stages of development. Due to its design its |
28 | Faster is in the early stages of development. Due to its design its |
| 29 | relatively safe to use (it will either work or simply slowdown the program |
29 | relatively safe to use (it will either work or simply slowdown the program |
| 30 | immensely, but rarely cause bugs). |
30 | immensely, but rarely cause bugs). |
|
|
31 | |
|
|
32 | More intelligent algorithms (loop optimisation, type inference) could |
|
|
33 | improve that easily, but requires a much more elaborate presentation and |
|
|
34 | optimiser than what is in place. There are no plans to improve Faster in |
|
|
35 | this way, yet, but it would provide a reasonably good place to start. |
| 31 | |
36 | |
| 32 | Usage is very easy, just C<use Faster> and every function called from then |
37 | Usage is very easy, just C<use Faster> and every function called from then |
| 33 | on will be compiled. |
38 | on will be compiled. |
| 34 | |
39 | |
| 35 | Right now, Faster can leave lots of F<*.c> and F<*.so> files in your |
40 | Right now, Faster can leave lots of F<*.c> and F<*.so> files in your |
