From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: common lisp vs elisp.
Date: Tue, 06 Jul 2021 03:53:47 +0200 [thread overview]
Message-ID: <87h7h89phw.fsf@zoho.eu> (raw)
In-Reply-To: YNlwNpd2CjVC4X9C@protected.localdomain
>> I want to make a 2D game tho, that's why I tried to get
>> SLIME and SBCL going, maybe one could do SDL2 with that and
>> have some sprites bounce off the ceiling...
>
> I don't agree to discussions of proprietary software on GNU
> mailing lists unless there is intention or project to make
> free software out of it.
What's proprietary, GOOL? Yes, Game Oriented Object Lisp
(GOOL) is proprietary [1]
What does it mean that the dialect is made for writing games?
You have to have that in _the actual language_ ? :O
Hm, also, what does it mean exactly when a *language* is
proprietary? Offer support, write a book? Not anyone can write
a compiler and/or other tools legally? Or not anyone can take
parts of the language to another language s/he is working on?
(Heh, were a lot of programming languages developed by women,
I wonder...)
But that doesn't matter in this/my case, I use Emacs, SLIME,
CL (SBCL), all free, right? This is how far I've got [2] -
right now I'm just adding stuff, no plan, and I won't need one
for a loong time since I can think of A LOT to add :)
I know you don't like to use Elisp in Elisp (e.g., cl-lib),
but it is OK to use in CL, right? Elisp, I mean?
[1] https://en.wikipedia.org/wiki/Game_Oriented_Assembly_Lisp
[2] https://dataswamp.org/~incal/cl/general-base/
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-07-06 1:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 2:22 common lisp vs elisp Hongyi Zhao
2021-06-20 3:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 3:26 ` Hongyi Zhao
2021-06-20 3:42 ` 2QdxY4RzWzUUiLuE
2021-06-20 4:04 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-20 4:44 ` Hongyi Zhao
2021-06-20 6:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 6:36 ` Joost Kremers
2021-06-20 6:57 ` Hongyi Zhao
2021-06-20 7:35 ` Jean Louis
2021-06-20 12:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-27 15:08 ` Andreas Eder
2021-06-27 15:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-28 6:46 ` Jean Louis
2021-07-06 1:53 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-07-06 12:28 ` Alexandre Garreau
2021-07-06 16:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 7:16 ` Jean Louis
2021-06-20 7:04 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7h89phw.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).