From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Next browser finally on master!
Date: Wed, 19 Dec 2018 22:45:00 +0100 [thread overview]
Message-ID: <87y38lry1v.fsf@elephly.net> (raw)
In-Reply-To: <87zht1i4nt.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> - As far as I understand, the compiler *does* change the resulting
> binary, thus the resulting REPL experience will be different, because
> all Lisps are different beyond the ANSI standard and other undefined
> behaviour. In other words, connecting via SLIME to ccl-next or
> sbcl-next would result in a different environment.
Sure. I wouldn’t expect people who use ECL to be able to load libraries
that were built with SBCL.
>> That these packages can *also* be used as libraries does not mean that the
>> packages should have names with the “sbcl-” or “cl-” or “other-lisp-” prefix.
>
> That would not be consistent with the Lisp library naming scheme then.
> And it raises the question as to why we have bothered with the sbcl- and
> ecl- prefixes so far.
The naming scheme applies to packages that are primarily used as
libraries. A package “foo” that is written in Python and also provides
modules that can be imported in an interactive Python session will not
be named “python-foo” when it is primarily used on its own.
--
Ricardo
next prev parent reply other threads:[~2018-12-19 21:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 10:34 Next browser finally on master! Pierre Neidhardt
2018-12-05 14:40 ` Benjamin Slade
2018-12-05 16:13 ` Pierre Neidhardt
2018-12-06 0:15 ` swedebugia
2018-12-06 8:31 ` Pierre Neidhardt
2018-12-06 9:38 ` Andreas Enge
2018-12-06 14:03 ` Pierre Neidhardt
2018-12-06 18:23 ` Andreas Enge
2018-12-06 18:24 ` Pierre Neidhardt
2018-12-06 18:29 ` Pierre Neidhardt
2018-12-06 21:02 ` Pierre Neidhardt
2018-12-09 16:19 ` Pierre Neidhardt
2018-12-09 16:21 ` Pierre Neidhardt
2018-12-19 13:40 ` Ludovic Courtès
2018-12-19 14:37 ` Pierre Neidhardt
2018-12-19 13:37 ` Ludovic Courtès
2018-12-11 7:18 ` swedebugia
2018-12-11 7:46 ` Pierre Neidhardt
2018-12-11 8:13 ` swedebugia
2018-12-11 17:11 ` Pierre Neidhardt
2018-12-19 13:35 ` Ludovic Courtès
2018-12-19 18:47 ` Brett Gilio
2018-12-19 19:03 ` Pierre Neidhardt
2018-12-19 19:08 ` Pierre Neidhardt
2018-12-19 20:32 ` Brett Gilio
2018-12-19 20:29 ` Ricardo Wurmus
2018-12-19 20:34 ` Brett Gilio
2018-12-19 21:32 ` Pierre Neidhardt
2018-12-19 21:45 ` Ricardo Wurmus [this message]
2018-12-19 21:48 ` Brett Gilio
2018-12-19 22:07 ` Pierre Neidhardt
2018-12-19 21:45 ` Brett Gilio
2019-01-03 4:32 ` Andy Patterson
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y38lry1v.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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).