WiiLi.org

[CarlKenner]

The first thing you need is a lexer, also known as a scanner, or tokenizer, to break up the code into words. In the real GlovePIE the same lexer is used for both the compiler and for the syntax highlighter.

The lexer in glovePIE is more complicated than normal. I recommend writing it yourself rather than using an automatic compiler generator. But start with something simple which should recognise the main keywords, and symbols like >=, and comments. The lexer needs a function to check what the current word/symbol is, and another function to move onto the next symbol.

The next thing you need is a parser. The parser in GlovePIE converts the entire script into a list of objects, each object representing a statement. Expressions are also stored in objects. Basically GlovePIE just goes through the list of objects, executing each one. You will probably need to write your own parser, rather than using a compiler generator, due to some complexities of the language.

The parser needs to start with a function called ParseLine which returns an object representing a command (or null for blank lines). This function will check what the first symbol is and then call appropriate functions like ParseAssignmentStatement, ParseIfStatement, etc.

Expressions need to be represented by objects. There needs to be an object for all kinds of expressions, eg. ConstantExpression, UnaryOp, BinaryOp, WiimoteField, KeyboardField, etc. Each expression object needs a function to get the value, a function to get the data type, a function to get the units, a function to set the value, etc.

The data types can be boolean, integer, scalar, 3d vector, 3x3 rotation matrix, or string. Booleans, integers and scalars are all stored as double precision floating point.

I'll explain some more later.

[abstrakraft]

Out of curiousity - why do you recommend against parser/lexer generators (e.g. yacc and lex)? I've written small languages of similar complexity to GlovePIE's, and I must say, I'd have nightmares about doing it manually.
_________________
"I seldom let practicality get in the way of my fascination with shiny things and blinky lights."
- some guy
http://abstrakraft.org/cwiid

[SwedishFrog]

Thank you Carl. I'd love to start implementing these things.

Expressions are stored as objects, eh? Neat trick.

What I'd like to know about is the design of the threading in GlovePIE. What I mean to say is, tell me about how you loop the script as a whole, and subsequently how you loop the insides of If statements and things like that.

[tic]

I dont understand what all the fuss is with the language. it will take a while, but should be simple enough. how to loop the script will be trivial.

the real answer i want to know is how the automatic connecting with bluesoleil works!?

[Cha0s]

BlueSoleil -> BlueCove -> WiiRemoteJ -> OpenPIE.

Simple. Swedish is right. We need to figure out the scripting. That'll be the hardest part. Mapping things to WiiRemoteJ functions should be a piece of cake.

EDIT: fixied my chain of connectiveness and added a comment on our priorities.
_________________
Cha0s

[SwedishFrog]

tic -- it depends alot on the implemention, so I'd like to know how carl went about it.

[tic]

so how is openpie coming along? is there anything that can be tested out? or some code I could have a look through?