YourWishes/jerryscript
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix formatting in API and internals

Browse Source
This commit is contained in:
Evgeny Gavrin
2015-06-14 16:39:31 +03:00
parent 841a8dc376
commit e669531811
3 changed files with 216 additions and 141 deletions
Download Patch File Download Diff File Expand all files Collapse all files
04.internals.md
+4 -6
View File
@@ -5,7 +5,7 @@ permalink: /internals/
---
* toc
{:toc}
{TOC}
# High-Level Design
![High-Level Design]({{ site.baseurl }}/img/engines_high_level_design.jpg)
@@ -59,9 +59,9 @@ Due to some limitations of the parser, some parsing functions take `this_arg` an
### Lexer
The lexer splits input string on set of tokens. The token structure (jerry-core/parser/js/lexer.h) consists of three elements: token type, location of the token and optional data:
The lexer splits input string on set of tokens. The token structure (`./jerry-core/parser/js/lexer.h`) consists of three elements: token type, location of the token and optional data:
``` c
```cpp
typedef struct
{
locus loc;
@@ -71,9 +71,7 @@ typedef struct
token;
```
Location of token (`locus`). It is just an index of first token's character at a string that represents the program.
Token types are are listed in lexer.h header file (`token_type` enum). Depending on token type, token specific data (`uid` field) has the different meaning.
Location of token (`locus`). It is just an index of first token's character at a string that represents the program. Token types are are listed in lexer.h header file (`token_type` enum). Depending on token type, token specific data (`uid` field) has the different meaning.
Token type | `uid` meaning
------------|--------------