4 ms·
If you were using a C compiler that produced executables that dynamically linked libc and other libraries, would you have any problems understanding that you ca
by anamax 18y ago
If you were using a C compiler that produced executables that dynamically linked libc and other libraries, would you have any problems understanding that you can't run those executables on a machine that doesn't have the relevant libraries?
The lisp environment is basically the run-time library for lisp programs. In some cases, that run-time can be statically linked. In others, it can't.
You wouldn't find this confusing wrt C programs, so why is it a hard concept wrt Lisp programs?
- gruseom 18y agoI think you're agreeing with tjr. The concept isn't hard, it makes perfect sense. What's puzzling is why it's hard to get a simple answer when you ask how to do it - or rather why the question itself is frowned upon.
- skolos 18y agoI don't think anyone argues or don't understand this concept. The problem is: instead of answering the question: "How do I create executable?" people got lectured on why they shouldn't do that. I think it is much more productive for everyone just to give an answer and then, once you get the usual follow up question quickly explain why executable is big. This way lisp community might get more users. But as it stands now all we hear is complaints that lisp community is bunch of jerks - the answers people get for this simple question is one of the reason why people think that the lisp community is not friendly.
- anamax 18y ago> I don't think anyone argues or don't understand this concept. The author of the original complaint clearly didn't. As he wrote: "I asked the question on Usenet, trying to explain that not everyone I wanted to give programs to had Lisp on their computer." Lisp is the run-time for lisp "executables". Just as one can't run a C executable that depends on a dynamically loaded libc on a machine that doesn't have a dynamically loadable libc, one can't run a lisp executable without the relevant run-time. This isn't an odd concept. Many windows programs depend on dlls.
- tjr 18y agoYou are correct in that I did not understand the matter when I first asked the question. However, the replies that I got did nothing to really answer it; it was just handwaving. That was ten years ago. I understand Lisp systems quite a bit better now, but I maintain that it is a valid question. Why? You have made the point that C programs can be built to rely upon dynamic libraries, and indeed they can, and this is similar to Lisp programs relying upon the Lisp runtime. However, C programs can also be built statically, and not have to rely upon additional libraries being present. This is not only possible, but fairly common, especially for simple programs. If a Lisp novice is trying to build, say, "Hello World," and expects a static executable as a result, why is that so much to ask? In fact, it is a lot to ask of Lisp, but if you are new to Lisp, you are not likely to understand why. I wouldn't expect a novice C programmer to write "Hello, World" such that it depends upon dynamic libraries; moreover, a novice ought to be able to stay busy learning C and writing ostensibly useful programs for quite a while without doing dynamic linking. Unfortunately, it seems that too many Lisp novices don't get the answer that you have provided (which is quite a useful answer). Instead, their question is brushed off as irrelevant. At least this has been the case in the past; I could not say if anything has changed.
- anamax 18y agoHuh? You said that you were a "C programmer" when you asked about running lisp executables. When someone says "I'm a C programmer", as most folks asking about "lisp executables" on comp.lang.lisp do, I think that it's reasonable to assume that they've heard of and understand dynamic libraries. Some lisps have static linking, some don't. I'm sorry that this was a show stopper for you. Would an "install shield" builder, as is typically used for windows programs, have helped? I don't suppose that you had the same reaction to Java, Python, Perl, awk, sed, tcl....
- tjr 18y agoWhen delivering an application to an end-user, hoops that the end-user has to jump through in order to run the application ought to be considered. The optimal route, in my opinion, is to deliver a totally self-contained application that doesn't require the user to install any runtime systems whatsoever. In that light, yes, Java is suboptimal. However, installing the JRE is pretty straightforward for end-users. Many users even already have the JRE installed. Asking an end-user to install CLisp is a whole other kettle of fish.