Smalltalk also has similar interactive development styles. One can build the application incrementally piece-by-piece. It has a residual graphical integrated development environment -> the development environment is a part of the program. It uses late-binding via message-passing. It starts and saves images (-> dumps of the heap contents, data and code). It is introspective & reflective (one can find out about the running program and can change it).
No, the compiler does not do that. If you look into your macro here, it just puts the args start and end back in. The generated code then is executed. Remember: START and END are bound to the source forms, not computed values.
In the original macro you had the form (loop for port from start to end ...), which you tried to compute at macro-expansion time. But the values of START and END are not necessary numbers, but source forms, like variable names.
If you compile code, then the compiler expands macro forms at compile-time. If you want to generate a variable number of let bindings, then the number needs to be known at compile-time.
start and end thus can’t be variables at run-time.
(let ((start 1))
(with-free-ports start 3 port-1))
If we compile above form, then at compile-time the value of start generally is unknown.
You compile the file compile.lisp. You don’t load it, you are compiling it.
That means: you compile the expression (ql:quickload "defstar"), but you don’t execute it. The file-compiler generates code for function calls, but does not execute them.
Then the package stuff does not know the package named “DEFSTAR”, because the thing has not been loaded.
See EVAL-WHEN:
(eval-when (:compile-toplevel :load-toplevel :execute)
(ql:quickload "defstar"))
Above makes sure that the enclosed form is also executed during compilation.
On my Mac with ABCL 1.9.2 I can load it via Quicklisp and get for example this error:
; Caught COMPILE-FAILED-WARNING:
; Lisp compilation failed while compiling
#
Proprietary implementation makes it hard to inspect what’s going on in the image and optimize the code comprehensively
If I were a paying Franz customer and I would be interested in SLIME/SLY improvements, I would kindly ask them to provide it. Maybe they would then just do it or ask the customer to pay for it. That’s what technical support is for.
Second: as a Franz customer one could get the source code for much of the product. I’m not a customer, but I guess this possibility still exists.
Allegro is not the ideal basis, especially for learning
I think it can actually be the opposite. Among new Lisp users GNU Emacs is often cited as a hurdle.
Allegro CL comes with an GUI based IDE on Linux, Windows, and Web browsers. This makes it possible to use it without GNU Emacs + SLIME/SLY. I consider that to be a feature. The IDE of Allegro CL has a bunch of features: https://franz.com/support/documentation/10.1/doc/cgide.htm#menus-dialogs-1
Best: the stuff is written all in Allegro CL itself and can be reused.
CMUCL is also way behind it platform support. CMUCL is mostly limited to being a 32bit application (IIRC). SBCL OTOH supports various 64bit platforms, incl. ARM64 on Linux and macOS.
CCL is mostly only on life support. The native port to the Apple Silicon Macs isn’t under way. CCL isn’t making any progress.
Allegro … So it actually is worse than open-source impls.
I doubt that this is generally the case.
CL-USER> (java:jstatic "sqrt" "java.lang.Math" 17.0d0)
4.123105625617661d0
That’s about the so-called “modern mode”, where standard Common Lisp symbols internally have lower case names (which violates the Common Lisp standard) and the default readtable case is :preserve. In the standard it is :upcase. Also other predefined symbols have lowercase names.
https://franz.com/support/tutorials/casemode-tutorial.htm
Is that incompatible language change used by other implementations?
See CLHS 1.4.1.4.1 Case in Symbols: http://www.lispworks.com/documentation/HyperSpec/Body/01_dada.htm
“As such, case in symbols is not, by default, significant.”
“The symbols that correspond to Common Lisp defined names have uppercase names”
The symbol will be interned in some package. A keyword symbol is in the package KEYWORD. That’s slightly better than to use the symbol of some other package, which “pollutes” that package with that symbol. ;-)
An alternative, out of fashion because of the upper case, is to use a string “FOOBAR”.
Why would you assume that?
READ mostly gives a tree of tokens. This makes it a form of a tokenizer. After we call READ we don’t know what the tokens mean: is FOO a variable, a macro, a function, a built-in special form, a type, … This can only be determined by interpreting/compiling the token tree.