Re: How Common Lisp sucks

In article <87zmijlee3.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
Pascal Bourguignon <pjb@xxxxxxxxxxxxxxxxx> wrote:
Ron Garret <rNOSPAMon@xxxxxxxxxxx> writes:

Cross-compiler portability for C and C++ is pretty good. It's even
pretty good for CL as long as you don't have to interface with the
outside world, which is exactly the problem.

I don't think so. Try to link a library compiled for the Darwin/ppc
virtual machine with your program compiled for the Linux/x86 virtual
machine.

I can't tell if this response was just meant to be silly or not;
apologies if misunderstood. I bet the original poster meant source
portability, not attempting to link shared objects from different
platforms into one executable..

Source cross-compiler portability for C and C++ is indeed quite good.
In my day job my product is largely C/C++ (with parts in Java and a
smattering of scripting languages around the edges). While I do all my
work on Solaris, the product ships on at least 5 different OS's across
several hardware architectures, using different compilers on every
platform. It is not a problem.

By the same token, it's hard to interface a library compiled for the
SBCL/x86 virtual machine with a program compiled for the clisp virtual
machine.

And yet it is not a problem with Java (or perl/python/ruby/..). In my
free time I sometimes write code for friends, some of whom run windows
(they are decent people otherwise). As I don't own any windows
machines at home, I write such code in Java, compile it into class
files on either Linux, Solaris or OS X and send the jar files to
friends who run the applications on windows. It Just Works. Is there
any way I can pull this off using lisp? (Serious question, I'd love to try!)

None of this is meant to detract from lisp. Lisp is fun and I'm
enjoying it a lot. But if we're going to compare languages, it's good
to be objectively honest about the facts. Some of the problems with
lisp are non-issues in other languages. Of course it cuts both ways,
obnoxious problems in other languages can become non-issues in lisp.


--
Jyri J. Virkki - Santa Cruz, CA
.

Relevant Pages

  • Re: a dozen cpus on a chip
    ... there are several compilers still available which implement ISO M2. ... By the time the full spec was published most industrial people had moved to other languages for purely commercial reasons. ... Some of the better static analysis tools for Modula2 can see into the program and find very deep faults that would not be found in normal execution. ... It is a common misconception that Lisp is always interpretted. ...
    (sci.electronics.design)
  • Re: merits of Lisp vs Python
    ... intelligent machines you need another path, that is what has not been ... Lisp compilers will generate better and better code. ... languages like C where much of the work has been done. ...
    (comp.lang.lisp)
  • Re: Is octave good to do image processing?
    ... But in any case I consider it untrue that a Lisp program is more ... modern languages and compilers are completely cache unaware. ... compilers that allow you to exploit the full power of your hardware. ... You know what languages hardware drivers are written in by the ...
    (comp.dsp)
  • Re: New Computer Language Shootout?
    ... In Lisp functions, variables and macros usually have longish names. ... compilers, I think. ... learned from the lisp culture and I use it in all the languages I ...
    (comp.lang.lisp)
  • Re: Why dont we have "C" machines? (was Re: [OT] Re: Should *most* memory be release back to the sys
    ... written either in assembler or other "system programming" languages like ... But now most operating systems are written in C, most compilers ... single task OSes, and multitasking OSes. ... OS (assuming that a lisp machine is the thing where you basically run ...
    (comp.lang.ruby)
Loading