shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

271
active users

#commonlisp

10 posts9 participants3 posts today

[1/2] In #CommonLisp, SBCL accepts directory pathname components which are subpaths and not names:

(make-pathname :directory '(:absolute "tmp" "foo/bar")) returns #P"/tmp/foo/bar/".

On CCL, the same form yields #P"/tmp/foo\\/bar/" which of course results in errors in a lot of contexts because "/" is not a valid character in filenames.

#embeddableCommonLisp's #ffi (*not* libffi) #commonLisp #Cxx #programming example - taking base64 encoding C++ function/namespace from @jeremy_list 's secure scuttlebutt implementation, and using it for extremely portable common lisp rather than nonportable haikuos C++. A straightforward but technical indicative example.

screwlisp.small-web.org/fundam

Though! My one seems to get half the out bytes wrong x_x Edit: I forgot three cdrs, now works 100%.

Anyway, the #ecl #example is working.

screwlisp.small-web.orgC++ and embeddable common lisp habitat example ~ base64 encoding

@awkravchuk hey, I'm going to talk to @kasper about #commonLisp #indie #gameDev (w/ #opengl iirc) at 8pm NZT tomorrow which I believe to be between between 8am and 12pm Sunday morning in much of Europe.

Kasper mentioned they would like to co-guest with you if you would like that (at admittedly short notice).

I think I missed a big announcement by you at some point previously as well. Would you like to visit / check in (in a one hour jitsi call #peertube #live #fedi)

#lisp When you have a working library, an easy way to get a terminal-based readline application in 2 lines:

dev.to/vindarel/common-lisp-a-

short post, efficiency gains inside… how useful is it for you for the day-to-day? (honest question. Do you have many lisp utils you'd use on the terminal?)

DEV CommunityCommon Lisp: a command-line interactive terminal application in 2 linesThe quicker to a MVP the better, right? Suppose you have a working Lisp function: (defun play...

#spatial #programming #commonLisp #leonardoCalculus

screwlisp.small-web.org/lispga

New organisms-2 knowledgebase,starting out with local spatial walking at @mdhughes mdhughes.tech/ recommendation that fast access to local neighbors is fundamental.

I.e. I don't want to check every organism in the world to check who is standing next to me. Well, I put that in a knowledgebase in my organisms-2 #KRF here.

Seems to work, pulls in 8 connected and 24 connected neighbors rightly.

screwlisp.small-web.orgLeonardo Calculus Knowledge Representation: Organisms 2 knowledgebase starting with local spatial walks
Replied to Vassil Nikolov

@vnikolov @tusharhero @evgandr @mdhughes @screwlisp

For me the one true editor was a dos program, qedit.

When I went to Linux I chose gedit as the most functionally equivalent to qedit even if it didn't have the feature set. When gedit lost it's way I followed pluma down the fork.

I am learning Emacs as an IDE for common lisp. My guru is @screwlisp and I am trying to understand his document.

screwlisp.small-web.org/fundam

I am totally uninterested in the vim/emacs wars.

screwlisp.small-web.orgInstalling common lisp etc like I use it geared for beginners
Replied to screwlisp

<">
I think some people do either end up not using slime, or not using sbcl’s ext:save-lisp-and-die to save and resume their universe lisp image core when they are using slime. When you should use both.
</">

Good points.
I'll make a weaker statement.
You don't _have_ to use them.
Your mode of operation will vary.
But you must make an __informed__ decision whether to use them or not.

#CommonLisp

@screwlisp

Replied in thread

> As much as CL is 'standardized', it doesn't appear to have a standard way of interaction with the ecosystem.

Aside:
as a language, Common Lisp _is_ standardized, no quotes.
Yes, it is unfortunate that (official) standardization didn't get around to doing more.
Simplistically, blame it on the first AI winter.

I think most people's problem with Lisp is that it wins no popularity contests.
Like Shakespeare's Banquo from the Play, it begat kings though it was none.

#CommonLisp

@phil @screwlisp

Unfortunately the state of graphics programming frameworks in #commonlisp is not quite there yet, so it seems I'll be crawling back to #cpp and #openframeworks for my graphics needs.

Bits and pieces are there in the lisp ecosystem, but there's nothing at the moment that ties it all together in the way that oF or Processing does. In the future I might think of going down the Clojure/quill route, as it seems I should be able to leverage the full power of a lisp and all of Java/Processing.