News for hackers. Stuff that matters.
Re:Why didn't Common Lisp fix the world? by adwf on Tuesday May 17, 2016 @06:10AM (#11712378)
Eval? The entire point of Lisp macros is toying around with evalulation in a safe fashion. It's other languages that do it so dangerously that gives eval a bad name. Lisp is the shining example of how to do it right.
Re:Why didn't Common Lisp fix the world? by chvid on Tuesday May 17, 2016 @06:43AM (#11712486)
AFAIK macros in Lisp are turing complete and executed at compile time.

This means (in principle) that there is no guarantee that a Lisp compile will ever terminate.

I don't know why the OP is been down voted. Lisp is not for everyone and every application; I think that is a perfectly reasonable point of view.

Re:Why didn't Common Lisp fix the world? by pjc50 on Tuesday May 17, 2016 @07:12AM (#11712592)
C++ templates are also turing complete, executed at compile time, and can result in extremely high compile times: http://cpptruths.blogspot.co.uk/2005/11/c-templates-are-turi...

I don't think that failure to terminate compiles is too big a problem in practice; treat it as just another form of compile-time error and fix your program.

Re:Why didn't Common Lisp fix the world? by chvid on Tuesday May 17, 2016 @08:00AM (#11712837)
It is a problem for tool support; one of the reasons why Java and C# has better editors.
Re:Why didn't Common Lisp fix the world? by sklogic on Tuesday May 17, 2016 @09:56AM (#11713633)
It's only a problem if your tools are done the wrong way. The proper tools can benefit from the macros instead. Of course, some discipline in how macros are implemented is required.
Re:Why didn't Common Lisp fix the world? by _ph_ on Tuesday May 17, 2016 @11:54AM (#11714652)
It is even better. Common Lisp macros are not a special macro language, but rather plain Lisp functions, which are run at compile time. This is important, because it means, you can write proper code in your development language for macro expansion instead of some obscure macro expansion language. This makes the process of writing macros rather robust and of course powerful. But of course, this means that like any program you write, you cannot guarantee that they terminate. For real-life macros that is rather a non-issue as they usually contain just a rather few lines of mostly simple code.
Re:Why didn't Common Lisp fix the world? by klibertp on Tuesday May 17, 2016 @07:32AM (#11712685)
The OP is being downvoted because he lies.

Common Lisp does have strong and optional static typing. It does have namespaces.

As for CL having `eval` - well, this is true at least. But I fail to see how in the world could that be a bad thing...

Re:Why didn't Common Lisp fix the world? by hga on Tuesday May 17, 2016 @07:57AM (#11712819)
A good implementation also has total dynamic type checking, and the better allow you to relax that for run time speed (although it was nearly free on Lisp Machines and can be pretty cheap on out of order superscalar CPUs like Intels, as long as you don't enable Hyperthreading which tends to use up the otherwise free execution engines that get used for it).
Re:Why didn't Common Lisp fix the world? by chvid on Tuesday May 17, 2016 @07:55AM (#11712813)
If a language has an eval construct it is hard/impossible to reason about types, security and correctness. It also makes it hard to compile it to machine code.
Re:Why didn't Common Lisp fix the world? by adwf on Tuesday May 17, 2016 @08:59AM (#11713195)
That would be true if we were talking about normal languages eval'ing strings. Lisp on the other hand treats the code as data and has the full compiler available at runtime. It can check types at both runtime and compile time, and it will still compile it down to nice machine code on the fly.

Lisp eval is not the same as other languages, you use it implicitly all the time. Any occurence of macros or something like `(1 ,(+ 2 3) 4) is playing around with evaluation behind the scenes.

Re:Why didn't Common Lisp fix the world? by sklogic on Tuesday May 17, 2016 @10:37AM (#11713990)
Macros do not need to be implemented with eval, unless they're lexically scoped macros. They're just normal function, normally complied just like anything else.

What is important is an incremental compilation, one top level statement at a time.

Re:Why didn't Common Lisp fix the world? by adwf on Tuesday May 17, 2016 @11:59AM (#11714687)
Yes, I didn't mean to imply that you needed to explicitly eval with macros. Rather that the nature of macros themselves is saying, eval this bit at compile time and that bit at run time. You are implicitly and safely doing what most languages would need an explicit eval call to do.
Re:Why didn't Common Lisp fix the world? by chvid on Tuesday May 17, 2016 @09:12AM (#11713293)
Parsing Lisp is not so hard, but as you said. It requires a JIT compiler or an interpreter. There are still some platforms/scenarios where that is not wanted.
Re:Why didn't Common Lisp fix the world? by sklogic on Tuesday May 17, 2016 @10:35AM (#11713977)
sbcl has `eval`, but it does not have a JIT compiler or an interpreter.