| 1 | And the differences between upstream and |
|---|
| 2 | ------------------ |
|---|
| 3 | |
|---|
| 4 | |
|---|
| 5 | And the differences between upstream and ○ |
|---|
| 6 | |
|---|
| 7 | String 1 Byte (ASCII) code |
|---|
| 8 | |
|---|
| 9 | ※ probably in Japanese ShiftJIS, EUC, UTF-8 that will be done in |
|---|
| 10 | |
|---|
| 11 | The type int, array definition and functions of the native words are ignored |
|---|
| 12 | Is a literal read-only. The operation has side effects and use a Clone |
|---|
| 13 | Must be (treated the same package) |
|---|
| 14 | |
|---|
| 15 | ○ unique extension |
|---|
| 16 | |
|---|
| 17 | Back to file the first line of comment # treatment (#! Execution) |
|---|
| 18 | |
|---|
| 19 | NIL # UNBIND Apart from the internal state (of special immediate value) is added. At present |
|---|
| 20 | # UNBIND input on how the syntax does not exist. NIL work the same way as on |
|---|
| 21 | Will be treated to |
|---|
| 22 | |
|---|
| 23 | Add operator == |
|---|
| 24 | |
|---|
| 25 | = Operator and stronger than the comparison |
|---|
| 26 | |
|---|
| 27 | Support for indefinite number of長引 |
|---|
| 28 | |
|---|
| 29 | Example: func (a1, a2, args ...) |
|---|
| 30 | A leader in 3-point args as the rest of the arguments the array will be binding. |
|---|
| 31 | |
|---|
| 32 | Add pointer with the magic name |
|---|
| 33 | |
|---|
| 34 | @ name format pointer of the Magic (Magic pointer with the name: Named Magic |
|---|
| 35 | Pointer) can be used. |
|---|
| 36 | |
|---|
| 37 | The magic of the original Newton pointer (@ 1 format) and can not be combined. |
|---|
| 38 | For compatibility "NewtConf.h" in the __NAMED_MAGIC_POINTER__ |
|---|
| 39 | Newton commented that the use of the original pointer magic |
|---|
| 40 | You can choose. |
|---|
| 41 | |
|---|
| 42 | Add the definition of a pointer syntax magic |
|---|
| 43 | |
|---|
| 44 | @ name: = (a: 1, b: 2); / / name pointer with Magic |
|---|
| 45 | @ 1: = (a: 1, b: 2); / / Newton pointer to the magic of the original |
|---|
| 46 | |
|---|
| 47 | Add a binary object of expression |
|---|
| 48 | |
|---|
| 49 | Binary objects in the original description could not be directly, |
|---|
| 50 | In the following syntax to write directly to a binary object that is able to |
|---|
| 51 | Did |
|---|
| 52 | |
|---|
| 53 | <# class: n1, n2, ....> |
|---|
| 54 | <# N1, n2, ....> |
|---|
| 55 | |
|---|
| 56 | ※ n1, n2, ... the numbers (in decimal, hexadecimal) |
|---|
| 57 | |
|---|
| 58 | Signed integer support 32bit |
|---|
| 59 | |
|---|
| 60 | Add a regular expression object representation |
|---|
| 61 | |
|---|
| 62 | / Regular expression pattern / Options |
|---|
| 63 | Example: / [a-zA-Z] + / im |
|---|
| 64 | |
|---|
| 65 | When the above regular expressions to perform (_proto: @ protoREGEX, pattern: "[a-zA-Z] +", option: "im") |
|---|
| 66 | Will be deployed as. |
|---|
| 67 | |
|---|
| 68 | Important: The actual use of regular expressions to protoREGEX extension library is required. |
|---|
| 69 | The library will depend on the extended features. |
|---|
| 70 | |
|---|
| 71 | ○ Other |
|---|
| 72 | |
|---|
| 73 | NewtonScript upstream to dump a function of the object |
|---|
| 74 | |
|---|
| 75 | fn: = '( |
|---|
| 76 | class: CodeBlock, |
|---|
| 77 | instructions: <# instructions: 0x27, 0x00, 0x08, 0xA8, 0x70, 0x02>, |
|---|
| 78 | literals: [literals: a], |
|---|
| 79 | argFrame: (_nextArgFrame: NIL, _parent: NIL, _implementor: NIL), |
|---|
| 80 | numArgs: 0 |
|---|
| 81 | ); |
|---|
| 82 | |
|---|
| 83 | call fn with (); |
|---|
| 84 | |
|---|
| 85 | And by expressing the original byte code NewtonScript to perform |
|---|
| 86 | . |
|---|
| 87 | > vertauschen |
|---|
| 88 | Eine bessere Übersetzung vorschlagen |
|---|