GitXplorerGitXplorer
N

moor

public
16 stars
2 forks
0 issues

Commits

List of commits on branch master.
Verified
f5f74cd9e57c0f446c60ca1eba3fbcfa531d56ff

Merge pull request #11 from jperon/patch-2

NNymphium committed a year ago
Verified
f2f830fe97c03c40839ed5fa0d529d1e113937c6

Compatibility with Lua < 5.2 and LuaJIT

jjperon committed 4 years ago
Unverified
6f636cee90fdf5a43c9ed89a6a2f3653a12c909e

Merge pull request #10 from Nymphium/update_v5.0

committed 8 years ago
Unverified
7466c6c0d8ed998461ae8228e4c60a4fad64940e

update to MoonScript v5.0

committed 8 years ago
Unverified
9329bd4adf83b2e20a2a968500aa7197055b64fd

Merge pull request #7 from Nymphium/busted_rockspec

committed 8 years ago
Unverified
3b04e1f677423db28baa89a7fe58895c6d4be23c

no compile

committed 8 years ago

README

The README file for this repository.

#moor

Build Status

MoonScript REPL

Demo

$ moor
moor on MoonScript version 0.4.0 on Lua 5.3
> for i in *{1,2,3}
?  for j in *{4,5,6}
?   print j
?  print i
?
4
5
6
1
4
5
6
2
4
5
6
3
> class Cls
?  new: =>
?   @a = 1
?   @b = 2
?   @c = 3
?
<1>{
  __base = <2>{
    __class = <table 1>,
    __index = <table 2>
  },
  __init = <function 1>,
  __name = "Cls",
  <metatable> = {
    __call = <function 2>,
    __index = <table 2>
  }
}

yes, dump objects with inspect.

This supports tab completion with linenoise, and the history is stored to ~/.moor_history

Module

you can call REPL in your code

...
local var = 10 -- it can be referenced by the repl
local newenv = (require'moor')({}, _ENV)
local hoge = newenv.foo
...

TODO

  • repl command (needed?)

License

MIT