unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Brett Gilio <brettg@posteo.net>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: multi-lingual guile: language strictness
Date: Fri, 13 Jul 2018 21:57:13 -0500	[thread overview]
Message-ID: <87zhyusewm.fsf@posteo.net> (raw)
In-Reply-To: <91fce743-6feb-da96-075f-bd1e123f14be@gmail.com>


Matt Wette writes:

> Hi All,
>
> I posed a question on #guile IRC last weekend asking for use 
> cases for making
> Guile
> multi-lingual. The use case that came up was the desire to use 
> Guile as an
> extension
> that supports multiple languages for users. To that end, I 
> wonder how important
> it is
> to make these extension languages meet published language 
> conventions or
> standards.
> I believe to do so is too difficult: the Guile community does 
> not have the
> volunteer
> workforce people to achieve this. I think it would be more 
> practical to look
> for
> reasonable approximations. If this is the direction to go, then 
> should Guile
> name
> these extension languages according to what they attempt to 
> mimic (e.g.,
> javascript),
> or rather rename to something that has a similar sounding name 
> (e.g.,
> guavascript), or,
> as another option, rename with an extension monicker (e.g., 
> javascriptx)?
>
> Matt

Is this possibility for making Guile multi-lingual a promised 
feature,
or more of a wishlist type thing? I'll have to think about some 
ways
that might be good to approach this, because the limiting
volunteer-community is definitely going to be an issue.



-- 
Brett M. Gilio
Free Software Foundation, Member
https://parabola.nu | https://emacs.org



  reply	other threads:[~2018-07-14  2:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14  2:53 multi-lingual guile: language strictness Matt Wette
2018-07-14  2:57 ` Brett Gilio [this message]
2018-07-14 13:53   ` William ML Leslie
2018-07-14 16:22     ` Hans Åberg
2018-07-14 18:45       ` Matt Wette
2018-07-14 19:09         ` Hans Åberg
2018-07-14 19:24     ` Brett Gilio
2018-07-14  7:04 ` tomas
2018-07-14 13:49 ` William ML Leslie
2018-07-16 21:00   ` Hugo Hörnquist

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=87zhyusewm.fsf@posteo.net \
    --to=brettg@posteo.net \
    --cc=guile-devel@gnu.org \
    --cc=matt.wette@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).