From: Nala Ginrut <nalaginrut@gmail.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: The Road to 2.2
Date: Wed, 22 May 2013 14:50:06 +0800 [thread overview]
Message-ID: <1369205406.2610.45.camel@Renee-desktop.suse> (raw)
In-Reply-To: <CA+U71=Pf53dioEBmH45cbVusWz0bLVDvgTzUOiXqWE7W7ZYw8A@mail.gmail.com>
On Wed, 2013-05-22 at 00:23 -0400, Noah Lavine wrote:
> On Sun, May 19, 2013 at 6:02 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>
> > Andy Wingo <wingo@pobox.com> skribis:
> >
> > > On Sat 18 May 2013 15:44, Noah Lavine <noah.b.lavine@gmail.com> writes:
> > >
> > >> I have a very small question, based on something I think you said
> > >> earlier - since the container will be ELF, will we call our files .so
> > >> now?
> > >
> > > We certainly can. Is it a good idea though?
> >
> > I’d vote for keeping .go, or at least something different from
> > commonly-used extensions like .so.
> >
>
> I don't think it's a big deal, but the reason I asked was that I'm afraid
> .go will become increasingly popular because of the Go language. .so also
> sort of hints at native compilation in the future, although that's not a
> very strong reason to choose it.
>
How about .glc or .glo?
But anyway, I don't think we should yield against a competitor.
> Noah
next prev parent reply other threads:[~2013-05-22 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 21:49 The Road to 2.2 Andy Wingo
2013-05-18 5:00 ` Nala Ginrut
2013-05-18 10:37 ` Andy Wingo
2013-05-18 13:44 ` Noah Lavine
2013-05-18 15:18 ` Andy Wingo
2013-05-19 22:02 ` Ludovic Courtès
2013-05-22 4:23 ` Noah Lavine
2013-05-22 6:50 ` Nala Ginrut [this message]
2013-05-19 22:06 ` Ludovic Courtès
2013-05-20 14:33 ` Andy Wingo
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1369205406.2610.45.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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).