You need to specifiy -b (or --break-chars) BEFORE ant -f (or --file ) options!
The -f options uses what is set in -b to split up the words, so in #commonlisp that means it will break on dashes unless you specify a dashless -b PRIOR to the -f option.
(specifying a dashless -b AFTER is not good enough)
Finally able to render (clim-demo:demodemo) and start a test from there. This has been a plateau barrier for me for a while and I was hoping to cross it before the new year. #McCLIM#Wayland#CommonLisp
I just finished my article on interactive #CommonLisp development. Turned out to more than I expected and less that it should be. One could probably write a small book on the subject. Hopefully it will still be useful.
In 1984, 40 years ago, Digital Press published the book "Common LISP: Reference Manual" by Guy L. Steele Jr. and others, more widely known as the first edition of "Common Lisp: The Language" or CLtL1. It was an early major milestone of a Lisp standardization process completed a decade later.
For the last 10 months I've been working on a #CommonLisp#EntityComponentSystem microframework, cl-fast-ecs, and I've just published a part 1 of in-depth tutorial for it. Let me know what you think 😊
This directory contains KR, a #kernel knowledge representation system. Unlike other systems, KR implements a small, carefully selected amount of functionality in order to keep performance within reasonable limits #commonlisp
I wanted to share a comprehensive cloud-init YAML file that I've put together
for setting up a robust server environment. It's tailored towards creating a
secure, user-friendly, and developer-ready setup right from the get-go. Here's
a glimpse of what it covers:
Locale, Keyboard, and Timezone Configuration: Sets up the basic locale,
keyboard layout, and timezone for the system.
User and Group Management: Creates system and regular users, assigns them
to groups, and sets up sudo and SSH key authentication.
Package Management: Installs a range of essential and useful packages,
including fail2ban, ufw, nginx, certbot, sbcl, emacs, git, and many more.
It also handles automatic package updates and upgrades.
Security Enhancements: Configures SSH, ufw firewall, and fail2ban for
better security.
Nginx Setup: Sets up Nginx with a reverse proxy and SSL using Certbot.
Git, SBCL, SLIME, and Quicklisp Setup for User: Sets up a ready-to-code
Lisp environment for the user.
I believe this setup can save a lot of time and ensure a solid foundation for
anyone looking to deploy applications or development environments on cloud
instances. It's especially geared towards those who prefer a Lisp-friendly
environment.
Feel free to use, modify, or suggest improvements to this setup. I'm open to
feedback and would love to hear your thoughts or experiences with similar
setups. Let's make server setup a breeze!
My blog @paolo is now on Planet Lisp. This aggregator of Common Lisp blogs and resources, one of my favorite Lisp readings, will syndicate only my posts about Common Lisp.
I am programming in #commonlisp to play random songs from a large mp3/flac collection.
It works fine in the REPL, but when I use it with #icecast it runs the program fresh each time.
You might see where I'm going. The naive random function must be deterministic so even though there is a series of random calls i am making to narrow down the choice, the choice is always teh same when the program is ran the 1st time.
the song isn't bad it's:
Kurt Vile and The Violators - Wedding Budz
@svw@rlonstein@glitzersachen@galdor I like early web mailing lists and forums. I like mailing lists because they don't require active participation, and also the time delay keeps people from rapid fire responding, and equalizes importance with ppl that post less.
I like forums because it is more direct and more fun to "just browse".
Either would be easy to setup nowadays, and maybe there's some tangential boost with the whole smolweb thing.
I hate it when someone tells me, "well Python and JavaScript can be programmed in functional programming style, so they are just as good as any other functional programming language," and "something something objects are the same thing as closures."
Then my program crashes and I spend 20 minutes debugging only to find that for the 100th time I wrote a method like this:
def getThing(self): self.thing
instead of like this:
def getThing(self): return self.thing
...where basically the problem is most of my program is written in functional programming style, except you STILL have to write the fucking "return" statement as the last line of the function.
If your language has "return" as a built-in control flow, it is hopelessly imperative not functional, and there is not a single monad framework or higher-order-function library anywhere that will make your language functional.
Stop telling me imperative languages like Python and JavaScript are just as good as functional languages, they are objectively worse than functional languages.
> "One of the reasons I like Python is that it can be used for so many different tasks, and without having to learn a new language.
@steriana@Pitosalas here is the thing though, Python is one of the worst languages for trying to adapt it to many different tasks.
If you want a truly general purpose high-level language that can be adapted to many different tasks, Common Lisp or Scheme is considerably better. The interpreters and compilers for these languages actually provide carefully designed mechanisms, like macro expansion and pattern matching, specifically for adapting the language to different tasks. This is possible because the syntax of the language is so simple and minimal that it is very easy to devise embedded domain specific languages (EDSLs) with very little effort, and without requiring people to expend the effort of learning whole new languages.
Python's syntax is relatively complex compared to Lisp, and its APIs for modifying the compiler and interpreter are not at all well-designed for adapting the language to various tasks compared to those of Common Lisp or Scheme. Creating EDSLs is for Python is not idiomatic coding style and discouraged, but people try to adapt it to every possible task anyways, and it becomes a horrible mess.
So you or anyone else, adressing the software industry as a whole, wanted to learn just one high-level language to solve every problem for you, it ought to have been #Scheme or #CommonLisp. Relatively speaking, #Python is so incredibly limited in what it can do compared to those languages, Python was objectively the wrong choice for this "lets adapt it to all purposes" way of thinking. The software industry is truly in a horrible mess as a result.
By the way, languages like Racket and Gerbil which are both built on top of Scheme are very easy to learn for beginners.