-
In LFE:
lfe> (> 2 1)
true
lfe> (> 3 2 1)
true
lfe> (> 1 2 1)
true
lfe> (< 1 2 3)
false
In CLISP:
[1]> (> 2 1)
T
[2]> (> 3 2 1)
T
[3]> (> 1 2 1)
NIL
[4]> (< 1 2 3)
T
-
The following commands need to be migrated
- [x] `info *` (see https://github.com/lfe/lfetool/issues/78)
- [x] `info bindir` command
- [x] `info erllibs` command
- [x] `info installdir` command
…
-
Originally filed here: https://github.com/lfe-rebar3/compile/issues/28
* a project with an lfe include and no additional settings in `rebar.confg`
* a project with no include but which uses the i…
-
In particular, modules `clj` and `cl` from LFE itself are not compiled, as they are written in LFE.
-
This is a follow-up to issue #167:
``` bash
$ ERL_LIBS=$ERL_LIBS:`lfetool info erllibs` lfetool download deps
```
``` lisp
exception error: undef
in (: lcfg clone-deps)
in (lfe_shell eval_form_1…
-
https://github.com/pcdshub/lcls-plc-lfe-motion/blob/dbcc58890e6511f8db291b972aa13b8cdbd2ae09/plc-lfe-motion/lfe_motion/POUs/PRG_AT2L0_SOLID.TcPOU#L30
Upstream issue with background https://github.c…
-
This can wrap `lfe_io:format` and be used simply as `format` when developers include `lfe/include/cl.lfe`.
-
Is this not maintained anymore? It doesn't work with any new version of lfe. (e.g. lfe 1.3)
-
There are three testing frameworks that should be supported:
* Erlang's eunit
* Erlang's Common Test
* the LFE ltest framework
Tasks
* [x] Examine each of the above and the most direct, straigh…
-
Part of epic #28