halunke 0.5.1 → 0.5.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/Gemfile.lock +1 -1
- data/docs/index.md +4 -2
- data/docs/stdio.md +2 -1
- data/docs/web.md +2 -1
- data/exe/halunke +4 -1
- data/lib/halunke/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 150c5430c572082097018606197faec2c0de858e
|
|
4
|
+
data.tar.gz: 8255a00970c4e932d7e37d47ceefa7ab0a454b2e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: e151c639862bfde2a262edd5854aff16e092562679210ca7bd9fe309b8e58d328676f6a97b78ded6ade6688ecaf448aebcbfbe9d533a9f5691f4aab710ef8eee
|
|
7
|
+
data.tar.gz: bc6b0cd941a258c18dc75b4a6ffb2c16f6ac3eb66ac7296eabb759d009fbb265d0ca02e3fcbb27082f379462b591241d415aa9eadd72dab7f0e7357ae7cb4085
|
data/Gemfile.lock
CHANGED
data/docs/index.md
CHANGED
|
@@ -31,7 +31,7 @@ Alternatively (if you don't have Ruby installed for example), you
|
|
|
31
31
|
can run it with Docker:
|
|
32
32
|
|
|
33
33
|
```
|
|
34
|
-
docker run --rm -ti
|
|
34
|
+
docker run --rm -ti moonglum/halunke
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
## How it works
|
|
@@ -82,7 +82,9 @@ Now you can send messages to `a` like `(a + 2)`. Why is there a `'` though? The
|
|
|
82
82
|
`'` signals an unassigned bareword. That means you can send it a `=` message
|
|
83
83
|
with a value, and it will assign it. Be aware that you can't reassign. So if
|
|
84
84
|
you assign something to a once, it will stay like this forever (within that
|
|
85
|
-
scope). Reassigning will result in an error.
|
|
85
|
+
scope). Reassigning will result in an error. *There will be reassignable
|
|
86
|
+
references in the future, see [the issue for
|
|
87
|
+
details](https://github.com/moonglum/halunke/issues/3)*
|
|
86
88
|
|
|
87
89
|
The values are also immutable. If you send a message to an object,
|
|
88
90
|
it will not change the object, but it will return an answer to you.
|
data/docs/stdio.md
CHANGED
|
@@ -3,7 +3,8 @@ title: Stdio
|
|
|
3
3
|
---
|
|
4
4
|
|
|
5
5
|
The object `stdio` is available from everywhere. *This will change in the
|
|
6
|
-
future. Interacting with STDIO is IO and will be
|
|
6
|
+
future. [Interacting with STDIO is IO and will be
|
|
7
|
+
isolated.](https://github.com/moonglum/halunke/issues/4)*
|
|
7
8
|
|
|
8
9
|
## `puts`
|
|
9
10
|
|
data/docs/web.md
CHANGED
|
@@ -3,7 +3,8 @@ title: Web
|
|
|
3
3
|
---
|
|
4
4
|
|
|
5
5
|
The object `web` is available from everywhere. *This will change in the future.
|
|
6
|
-
Interacting with STDIO is IO and will be
|
|
6
|
+
[Interacting with STDIO is IO and will be
|
|
7
|
+
isolated.](https://github.com/moonglum/halunke/issues/4)*
|
|
7
8
|
|
|
8
9
|
You can send the `run on` message to `web`. It expects the first object to be
|
|
9
10
|
your application (more on that later) and the second one the bind address and
|
data/exe/halunke
CHANGED
|
@@ -1,12 +1,15 @@
|
|
|
1
1
|
#!/usr/bin/env ruby
|
|
2
2
|
|
|
3
|
+
require "halunke/version"
|
|
3
4
|
require "halunke/interpreter"
|
|
4
5
|
require "readline"
|
|
5
6
|
|
|
6
7
|
interpreter = Halunke::Interpreter.new
|
|
7
8
|
|
|
9
|
+
Readline.completion_proc = ->(*) {[]}
|
|
10
|
+
|
|
8
11
|
if ARGV.length == 0
|
|
9
|
-
puts "Halunke REPL. Ctrl+d to quit"
|
|
12
|
+
puts "Halunke #{Halunke::VERSION} REPL. Ctrl+d to quit"
|
|
10
13
|
while (line = Readline.readline(">> ", true))
|
|
11
14
|
begin
|
|
12
15
|
value = interpreter.eval(line)
|
data/lib/halunke/version.rb
CHANGED