repl

Despite ample evidence to the contrary, #Ilive (hmm, if I were also #evil, that would be a pallindrome as well as a visual collision)
Fascinating (if I do say so) #lispgames #gamejam #gamedev #retrospective on #itch_io
https://lispy-gopher-show.itch.io/lispmoo2/devlog/834615/princess-revisited
I am enormously happy with the
{ verb [ dobj [ prep iobj ] ] } x
language dynamic, and how it shares your #lisp #repl, and their concerns are just... Different so they don't collide.
I guess I get my #languageDesign friends a little better now.
Thoughts?

Trivial memory cardgame in the #commonLisp #repl . (Er, using #McCLIM presentations).
https://screwlisp.small-web.org/lispgames/memory-game/

A good beginner example.

As I reveal in the thrilling conclusion

https://screwlisp.small-web.org/lispgames/memory-game/#conclusions

this small post is a step on the way to using xhtmlambda to generate a kitten webgame soon.

CLIM-USER> (reveal (elt *cards* 3))
T
CLIM-USER> (disp)
X,X,3,1,2,3
G3648,G3647
NIL
CLIM-USER> (reveal (elt *cards* 0))
NIL
CLIM-USER> (disp)
1,X,3,X,X,3
G3644,NIL

Sharpsign #lispgames #programming

So my question is, what's an intuitive way to use dropping-in- #fortran from the #lisp #repl ?
Reading a .f file ~ into a let* form which I'm currently doing seems kind of bland. #f( this(1) = is(2) + a / fortran * line) seems kind of uninspiring (who would want to express themselves like this). Maybe Enter "fortran mode" and read lines of fortran from *standard-input* with normal interactive evaluation hacked in?

The fortran becomes #series expressions in lisp.