wtf markdown

master
Jordan Orelli 10 years ago
parent 5ef3aad074
commit f63875b86a

@ -35,7 +35,8 @@ format in Go projects. The syntax is fairly similar, with a few changes:
json and similar formats parse text and render some kind of parse tree. We do
the same thing in moon, but then we walk the tree and evaluate it, which is why
variables are a thing.
variables are a thing. It's effectively just enough of a dynamic language
interpreter for variables to work.
# Types
@ -44,33 +45,33 @@ Moon defines the following types:
- integers: right now this is an int based on Go semantics; it's a 32 bit int
on 32 bit CPUs, and a 64 bit int on 64 bit CPUs. These are some integers:
```
1
2
-1
-12348
0
+0
1
2
-1
-12348
0
+0
```
- floats: they're all float64. These are some floats:
```
1.0
1.2
-9.3
3.14
1e9
1.0
1.2
-9.3
3.14
1e9
```
- complex numbers: they're complex128 values in Go. These are some complex numbers:
```
1+2i
-9+4i
1+2i
-9+4i
```
- strings: they're strings. They're not explicitly required to be composed of
UTF-8 runes but I haven't really been testing binary data, so for the moment,
all bets are off here. They're quoted, but maybe I'll go back on that.
These are strings:
```
"this one"
'that one'
"this one"
'that one'
```
You can use single or double quotes. Escape quotes with a backslash.
- objects: or maybe you call them hashes, objects, or associative arrays. Moon
@ -80,23 +81,23 @@ Moon defines the following types:
Also there are no commas between the values but I'm not sure I like this yet,
so it might change. These are some objects:
```
{name: "jordan" age: 28}
{
one: 1
two: "two is also a number"
pi: 3.14
}
{name: "jordan" age: 28}
{
one: 1
two: "two is also a number"
pi: 3.14
}
```
- lists: they're `[]interface{}` values. They're not typed, and they can be
heterogenous. Values are separated by spaces. I might put commas back in,
that's kinda up in the air right now. These are some lists:
```
[1 2 3]
[
"one"
2
3.14
]
[1 2 3]
[
"one"
2
3.14
]
```

Loading…
Cancel
Save