Fix Internals and remove favicon
This commit is contained in:
+3
-3
@@ -5,7 +5,7 @@ permalink: /internals/
|
||||
---
|
||||
|
||||
* toc
|
||||
{TOC}
|
||||
{:toc}
|
||||
|
||||
# High-Level Design
|
||||

|
||||
@@ -416,7 +416,7 @@ Otherwise, object's property set is iterated fully and corresponding record is r
|
||||
|
||||
ECMA-defined runtime operations are implemented mostly with routine having the following signature:
|
||||
|
||||
`ecma_completion_value_t ecma_op_* ([ecma_value_t argumants])`
|
||||
`ecma_completion_value_t ecma_op_* ([ecma_value_t arguments])`
|
||||
or
|
||||
`ecma_property_t * ecma_op_[find/get]*_property (objs, name string, ...)`
|
||||
|
||||
@@ -453,7 +453,7 @@ Rules for completion value are the same as rules for values, contained in them.
|
||||
## Opcode handler structure
|
||||
|
||||
Most opcode handlers consists of the following steps:
|
||||
1. Decode instruction (i.e. extract "idx"-s)
|
||||
1. Decode instruction (i.e. extract `idx`-s)
|
||||
2. Read input values from variables/registers
|
||||
3. Perform necessary type conversions
|
||||
4. Perform calls to runtime
|
||||
|
||||
BIN
Binary file not shown.
|
Before Width: | Height: | Size: 318 B |
Reference in New Issue
Block a user