lispm

64 ms·

691.
by lispm 3y ago
Yes, the ephemeral GC was a huge improvement.
692.
by lispm 3y ago
very cool!
693.
by lispm 3y ago
(defun foo (a) (+ a 1)) is a s-expression. For evaluation Lisp expands the DEFUN macro then and this returns a new s-expression. Which then is evaluated. > So are these "specials" being parsed by a grammar? Every special operat
694.
by lispm 3y ago
(quote a b c) does not exist in Lisp. QUOTE takes exactly one argument, the object to quote. It's a special operator . '(a b c) is (quote (a b c)) > defun = special form DEFUN is not really a form in the standard. It&#x
695.
by lispm 3y ago
> I think most special forms do not complicate syntax, as they look like your standard s-expressions Take LET: (let ((a b) (c d) e (f g)) (declare (type integer a)) (+ a b c d e f g)) It does not look like (foo arg0 arg1 .
696.
by lispm 3y ago
> The code works just fine in Common Lisp It would work fine in Lisp in general, since Lisp is typically late bound and can call global functions via the symbols. Thus in a function writing a call to an undefined function is not an error
697.
by lispm 3y ago
Personally I find Common Lisp in some cases slightly uglier, but clearer. (define foo (make-foo)) What is it? A function or a non-function? I prefer the Common Lisp version: (defvar *foo* (make-foo) "*foo* is the current
698.
by lispm 3y ago
CL-USER 21 > (let ((n 7) (report '(report))) (flet ((revise (report) (cons 'revised report))) (do ((report report (revise report))
699.
by lispm 3y ago
There is still money from the current budget. The problem is that digitalization is just one of the problems we have. Currently we are paying billions for energy related issues, for the Ukraine war and investing lots into the military indus
700.
by lispm 3y ago
How do you enforce that? Experience shows that most companies ignore that code is only for non-commercial use and it's hard to enforce for small companies. I also doubt that all customers are like Boeing.
701.
by lispm 3y ago
Objects are instances of classes in CLOS. Classes, Methods, Generic Functions, ... are also instances of classes. Classes support multiple inheritance. Instances have an identity, slots and a class. CLOS does not use methods attached to cla
702.
by lispm 3y ago
> Yes, but what makes us believe they won't go the same faith as all the others? Switching to an open source model would mean that only 1% of the users would pay anything. To make that viable you need a good business model for a muc
703.
by lispm 3y ago
> If LW and Franz are going to survive and not go same way as Symbolics, Sun & Co, they should probably rethink their strategy of licensing their stuff free for GPL/non-commercial use, similar as Qt and some other companies do.
704.
by lispm 3y ago
> Monkey patching comes from Ruby My Lisp Machine's operating system (MIT, end 70s onwards) is written in an object-oriented Lisp (using Flavors and later CLOS). Everything is open and everything can be changed at runtime. Mixins an
705.
by lispm 3y ago
Remember when you learned how recursion works? This is a similar case. You'll learn how to understand how a Lisp interpreter works. You'll get an extremely simple one, which is written in itself. The same primitive language which
706.
by lispm 3y ago
Interlisp for example used a spellchecker for its Lisp. See DWIM (Do What I Mean). Chapter 15: https://larrymasinter.net/86-interlisp-manual-opt.pdf In Genera the command "Find Symbol" has com-find-symbol as a sym
707.
by lispm 3y ago
> What do you think put them out of the business? Just the economy or some other more technical reason? The main reason was the end of the cold war and the end of the high-tech war. Means there were too few commercial customers. Where th
708.
by lispm 3y ago
I once (2012) gave a small Lisp talk at his company in Monheim (Rhine) on his invitation. Too early gone...
709.
by lispm 3y ago
> they can't distinguish between calling (foo 1 (+ 1 2) (+ 3 4)) and calling (foo 1) (+ 1 2) (+ 3 4). It uses always (foo 1 (+ 1 2) (+ 3 4)). It uses the complete input. > I don't even know if sly/slime repl even suppor
710.
by lispm 3y ago
One doesn't need to use the menus, one can use the keyboard commands. The UI provides several ways to interact: key commands, interactive command line and menus. > I see it has same ancestor as texinfo Genera comes with a Scribe-bas
711.
by lispm 3y ago
> how did they implemented it if you know? It's relatively easy: a variable: CL-USER> foo an operator with no arguments: CL-USER> (foo) an operator with one or more arguments: CL-USER> foo 1 CL-USER> foo 1 2 CL-USER>
712.
by lispm 3y ago
Most of my Apple laptops I have given to other people who have used them for years. Of the three M laptops I have (including the first M1 Air), none has any issues so far. If one breaks, I would let it repair at Apple. My personal main Lapt
713.
by lispm 3y ago
I would think that many/most Lisp implementations implement fixnum integers with tags. But many also have automatic overflow into bignums, like in Common Lisp.
714.
by lispm 3y ago
I once recorded a demo video, running Concordia on an actual Symbolics Lisp Machine. https://vimeo.com/83886950
715.
by lispm 3y ago
One of the ideas of Lisp is that you can extend/change the language to bring it near the actual domain level. The so-called "Embedded Domain Specific Language" is common in Lisp.
716.
by lispm 3y ago
"Lisp Lore: A Guide to Programming the Lisp Machine" by Bromley&Lamson was also written using Concordia AFAIK. The Symbolics documentation also has Jensen&Wirth "Pascal User Manual and Report" and Harbison &
717.
by lispm 3y ago
> They're not as robust as full boat CLOS classes Structures support single inheritance, CLOS classes support multiple inheritance. The main reason for structures is that they are faster to use by default - but they are less flexibl
718.
by lispm 3y ago
Lisp?
719.
by lispm 3y ago
A bit more from RPG about CLOS: https://dreamsongs.com/CLOS.html The CLOS spec was a collaboration of: Linda G. DeMichiel, Richard P. Gabriel (short RPG) : both from Lucid, Inc. Sonya E. Keene, David A. Moon : both from Sym
720.
by lispm 3y ago
> When I develop in a compiled language "batch compiled from scratch" OTOH, most usage of Common Lisp is compiled, often by an incremental in-image compiler > because oops I was actually still calling that deleted function s

More ›