4 ms·
Compilers usually leave some kind of footprint, usually in the form of some kind of runtime. Running `nm <myapp>` makes it pretty clear there is a Lisp system
by jlongster 17y ago
Compilers usually leave some kind of footprint, usually in the form of some kind of runtime. Running `nm <myapp>` makes it pretty clear there is a Lisp system there.
Still, I doubt hey would enforce it. But you can't build a business around it anymore, it's just too risky.
- lispm 17y agoI guess there are some Lisp to C compilers that don't need much of a runtime. Candidates for that are Stalin, the 'Lisp to C' compiler, ThinLisp, CLICC and some others. The 'Lisp to C' compiler was developed to create readable and maintainable C code.
- jlongster 17y agoYou are right. There's really no way they can reliably detect where the code came from. In fact, it should be pretty difficult to generally, but unfortunately, this clause will scare off business built around this. There's also PreScheme, which is one of my favorites. It's subset of Scheme which simply generates a few C functions that use a bunch of stack variables and gotos without any runtime.
- wtn 17y agoWhy do you think it's unfortunate? Won't that mean less competition for anyone who can reliably pass Apple's scheme-to-C "Turing test"?