BEE Lisp
in [Lisp]
|
From: Sufferer on 16 Mar 2010 16:13 Guys, what are you talking about? How can it be a "misguide attempt" like someone said here Being a C++ programmer, I found this implementation to be very comfortable to me. Yes, their example are very C-styled, but it makes BEE Lisp very C- programmer friendly implementation. I feel uncomfortable wrtiting true lispy code since I am a beginner in Lisp. So I think, for C++ programmer, willing to try lisp, BEE Lisp it the best implementation. I have some experience in disassembling and I looked into BEE Lisp executable of LISPPAD.EXE, a clone of notepad but in BEE Lisp. Well, it is not a compiler to native code. But it is not a byte-code one. It looks like a hybrid of native and byte code mixture. I suppose it is done to preserve mutable nature of lisp code - i.e we still may change functions bodies in runtime and I beleive this is possible because there are byte code in EXE (and some functions have native code inside). And, another benefit is that it allows to make dlls and then use them from C++ code so that I can combine my C++ code with lisp. So, lispy things can be coded and lisp and the most other project - in C++. It's very convinient. I think it is good implementation. Esepcially for C++ programmers.
From: Tamas K Papp on 16 Mar 2010 16:32 On Tue, 16 Mar 2010 13:13:58 -0700, Sufferer wrote: > Guys, what are you talking about? How can it be a "misguide attempt" > like someone said here Being a C++ programmer, I found this > implementation to be very comfortable to me. Yes, their example are > very C-styled, but it makes BEE Lisp very C- programmer friendly > implementation. I feel uncomfortable wrtiting true lispy code since > I am a beginner in Lisp. The only reason to learn Lisp is to write idiomatic code in it. If you want to write C/C++ code, use C/C++. If you want to learn Lisp, pick a decent dialect. > I have some experience in disassembling and I looked into BEE Lisp > executable of LISPPAD.EXE, a clone of notepad but in BEE Lisp. Well, > it is not a compiler to native code. But it is not a byte-code > one. It looks like a hybrid of native and byte code mixture. I > suppose it is done to preserve mutable nature of lisp code - i.e we > still may change functions bodies in runtime and I beleive this is > possible because there are byte code in EXE (and some functions have > native code inside). And, You can change functions at runtime in CL, too, by defining/recompiling a different version. This is done routinely during development, for example. It has nothing to do with bytecode, eg SBCL will cheerfully replace compiled code. > another benefit is that it allows to make dlls and then use them > from C++ code so that I can combine my C++ code with lisp. So, lispy > things can be coded and lisp and the most other project - in > C++. It's very convinient. I think it is good > implementation. Esepcially for C++ programmers. Most dialects of Lisp have foreign function interfaces, which you can use to interface to C/C++/... code. If you are interested in Lisp, you can find dialects that are incomparably better than BEE Lisp -- for free! Stay away from BEE Lisp, it looks like a scam for the unwary. I am sorry that you fell for it, but so far it seems that you only lost 30 euros, so you can contain your losses by dumping it immediately. Tamas
From: Futu Ranon on 16 Mar 2010 16:45 On Tue, 16 Mar 2010 16:13:58 -0400, Sufferer <dmazhartsev(a)gmail.com> wrote: > I feel uncomfortable wrtiting true lispy code since I am a beginner in > Lisp. What are you doing with it, exactly? Why'd you choose Lisp? Why BEE Lisp?
|
Pages: 1 Prev: Anyone willing to sell "On Lisp"? Next: Shibboleth authentification? |