diff options
Diffstat (limited to 'LuaSL/README')
-rw-r--r-- | LuaSL/README | 24 |
1 files changed, 4 insertions, 20 deletions
diff --git a/LuaSL/README b/LuaSL/README index c02b180..c019fb7 100644 --- a/LuaSL/README +++ b/LuaSL/README | |||
@@ -5,6 +5,10 @@ compatability first, then adding Lua extensions. It aims to replace the | |||
5 | woeful XEngine from OpenSim, and at a later stage, be the basis for a | 5 | woeful XEngine from OpenSim, and at a later stage, be the basis for a |
6 | client side scripting engine. | 6 | client side scripting engine. |
7 | 7 | ||
8 | To compile this, you will need Enlightenment Foundation Libraries (EFL) | ||
9 | installed in either /opt/e17 or /usr. These are typical places it get's | ||
10 | installed in. | ||
11 | |||
8 | 12 | ||
9 | Design. | 13 | Design. |
10 | ------- | 14 | ------- |
@@ -61,23 +65,3 @@ etc. | |||
61 | 65 | ||
62 | Performance testing will have to be done on 5000 scripts, to see how | 66 | Performance testing will have to be done on 5000 scripts, to see how |
63 | that compares against XEngine. | 67 | that compares against XEngine. |
64 | |||
65 | |||
66 | Parser. | ||
67 | ------- | ||
68 | |||
69 | The SL viewer code includes a flex/bison based parser that generates C++ | ||
70 | code that depends on various other bits of LL source code. It's GPL 2, | ||
71 | though the flex and bison source files includes no license text. | ||
72 | |||
73 | Flex is BSD and written in C. Bison is GNU (GPL 3 since 2.4.1, 2.3 is | ||
74 | GPL2) and written in C. It used to include info that stuff generated by | ||
75 | bison had to be GPL. Berkeley YACC is public domain, and written in C. | ||
76 | There is also btyacc, based on the berkeley version, but with some | ||
77 | useful extras. btyacc version 3 (the version coming from my version of | ||
78 | Ubuntu) apparently no longer supports C, only C++. It's written in C | ||
79 | though. | ||
80 | |||
81 | Let's see if flex and btyacc will do the trick, and output C. Might be | ||
82 | best to have the LSL to Lua converter as a seperate executable. Think | ||
83 | I'll end up writing my own parser. | ||