unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Germán Diago" <germandiago@gmail.com>
To: guile-devel@gnu.org
Subject: Interest in windows native port, interpreters for other languages and C++ binding API.
Date: Tue, 31 Jan 2017 11:28:50 +0700	[thread overview]
Message-ID: <CAALp5N5rPb1LJ=No42CO=gW25pwKNHp+7bpXxjNZHV5vgwAY-w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2401 bytes --]

Hello everyone,

WARNING: I cannot commit to any of the work below but I would try to do a
build system port if that makes sense.

I have been trying guile for a while lately (again). So far, so great!
Congratulations for this amazing piece of software. I am interested in
making real use of it in two main areas: as a general scripting engine and
for embedding in games.

Racket is also very mature and very good as a platform, but I would like to
put my effort in helping in guile maybe, especially because I use it as an
alternative to python and because guile supports native threads.

Here my questions:


1. As a general scripting engine, even if I love scheme, I know people do
not use it much, so this becomes kind of a social problem in team usage:
what is the status and roadmap to port: javascript, lua and python? I would
like to be able to use as an alternative inside guile. What is the effort
to complete javascript (I think it was started) in man-hours?

2. Windows works under POSIX. What would be the effort of doing a port to
native windows threads? Effort in man-hours?
3. Is there any interest in switching to meson build system? I think that
it works very well already and supports windows much better than autotools.
I have used it myself and it is improving day by day. I think it would be
reasonable to do 2. and 3. together if there is will. I could help
converting the project to meson as experimental myself.  Effort in
man-hours?

4. Interoperability: I was planning at some point, but I do not know if I
will find the time, to find a painless (as painless as Chaiscript for
example) way to bind scheme to C++ directly (not C), because it is the main
language I make use of. So maybe I could make use of the native bindings
and put a thin layer on top of it. Right now it makes a lot of sense for me
as a C API but I find it too verbose to use from C++: in C++ maybe I could
do better, something more similar to Chaiscript or
https://github.com/pybind/pybind11.


All this said, I am kind of a rookie still in scheme, but I am enjoying it
like no other dynamic language before :)

I would like to see guile succeed and I think that supporting more
languages is critical given that scheme's popularity is not as big as
python's or javascript's, but it is still possible to do so much more in
guile that I would not like to lose the chance to use it.

Thanks for your time.

[-- Attachment #2: Type: text/html, Size: 2796 bytes --]

             reply	other threads:[~2017-01-31  4:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31  4:28 Germán Diago [this message]
2017-01-31 15:29 ` Interest in windows native port, interpreters for other languages and C++ binding API Eli Zaretskii
2017-02-01  5:18   ` Germán Diago
2017-02-01 12:56     ` Eli Zaretskii
2017-02-01 15:09       ` Germán Diago
2017-02-01 13:39     ` David Kastrup

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='CAALp5N5rPb1LJ=No42CO=gW25pwKNHp+7bpXxjNZHV5vgwAY-w@mail.gmail.com' \
    --to=germandiago@gmail.com \
    --cc=guile-devel@gnu.org \
    /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).