Parser:Type resolver


(Redirected from Parser: Type resolver)
Jump to: navigation, search

Many aspects of EDL as inherited from GML conflict or seem inefficient when compared with a C++ environment. Also, C++ isn't exactly a jewel in many cases, either. For example, C++ requires pointer-based access to use -> instead of the traditional dot. GML offers switch() of multiple types, but is sadly inefficient at doing so, employing an O(N) segment of if()s. GML's dot operator treats the left-hand operand as an integer, and accesses the right-hand member, where C++ expects a const& instance to the left and accesses the member named to the right in that.

These conflicts could be resolved to improve upon both languages with the use of a good type resolution system.


The parser is stack-based, and operates off of a structure containing a number of identifying variables. The structure is as follows:

    string op; // What would follow the word "operator" if overloaded
    externs *type; // The type we would return if this were it for the stack: this tracks all referencing!
    unsigned otype; // The kind of operator this is; binary or unary, for example
    unsigned short prec; // The precedence integer of this level.
    unsigned short pad; // The number of & referencers on top of our existing ref stack
    rf_node *deref; // The rf_node of the next dereference needed, or NULL if conked out



The image to the right shows a sample expression being evaluated for type. Red gradated cells are the ones being operated on. Green gradated cells show the result. Result cells that are being operated on are shaded yellow. The columns show the type being stored (if any), the symbol the operator represents (if any), and the precedence of the operator represented (if there is an operator).

Here are a few simple rules implemented when evaluating an expression:

Personal tools