Du kan inte skicka meddelanden eftersom endast medlemmar kan göra det och du för närvarande inte är medlem.
Beskrivning:
Discussions, question and what not regarding LFE.
|
|
|
REPL search tool for functions
|
| |
Hi. I have a small _experiment_ going on here [1] that I wish to share. It's a search tool for functions. Also, a faster way of looking up Erlang functions. As you may imagine, it's not for every module out there. The syntax is: (query <module> (where <arguments> '-> <output>)) ...(#(fail (== (: lists concat '(3 1 3)) '(1 3)) '"313")... mer »
|
|
|
LFE is wonderful! Question about inconsistent behavior when matching
|
| |
Hello, Mr. Virding: I want to tell you first of all how much I like your lisp front-end to erlang. It makes using erlang -- as good a system as it is -- that much more pleasurable to use. It has made me so productive that, from now on, I will be implementing most of my high-level modules in LFE. I will continue to design the lower-level ones in erlang, however,... mer »
|
|
|
In the pipline
|
| |
...- When OTP documentation tools are properly available convert all documentation to use them. I am not a fan of edoc! Getting old, Robert
|
|
|
In the pipeline
|
| |
Here are some things which are in my immediate pipeline for LFE: - The interpreter, lfe_eval, does not handle macro expansion properly, fix this. - Guards are a mess now if you want more complex guards, it's not at all clear, fix this. - Improve the user_guide.txt documentation adding a new section on... mer »
|
|
|
Git and github
|
| |
Using github to work on LFE is a Good Thing. Forking LFE and telling me when there is something to pull makes it easy for me to incorporate changes. But it is even better if you create your own branches to do it in and don't use either master or develop; pretty much like with otp. This make is it easier for me to keep my branches clean and... mer »
|
|
|
LFE examples
|
| |
Getting back in the groove now after Christmas/New Year. A few days ago Mats (cadar) asked me what requirements I have for LFE examples. Very few actually and not that difficult: - A simple copyright which allows people to load, run and modify the code. - An interesting, fun, different, etc piece of code. If it is... mer »
|
|
|
shell automation using screen
|
| |
A bit off topic but I found it useful. To automate repetitive tasks I use "screen -X stuff $'<command>'" to start, load and test my code. The stuff command send characters to a started screen session. It works great. This is the script: --------------------- ...function run { screen -X stuff "$1"... mer »
|
|
|
record_info macro
|
| |
Hi, I'm working on some code that use records. At the moment record_info is missing. To solve that I tried to create a macro with the goal of only making me declare the record in one place. How to do this in a better way? Some one may have already tried this. --- (eval-when-compile (defun def_record_funs ()... mer »
|
|
|
Support for Erlang hrl files
|
| |
The main roadblock for me in interop with erl code is hrl files. Some of the core erlang libs use them ( [link] ) and they are _AFAIK_ unavailable inside LFE. I know robert mentioned it was going to be hard to do that (last spring). Any update? What can we do for erlang code that needs Erlang... mer »
|
|
|
|
