unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: msematman@myopera.com
To: guile-user@gnu.org
Subject: Re: guile scripting for gdb
Date: Sat, 30 Nov 2013 10:15:14 +0100	[thread overview]
Message-ID: <1385802914.11498.53756421.78A1B0B8@webmail.messagingengine.com> (raw)
In-Reply-To: <87ob5vlr2s.fsf@gnu.org>

I'm curious, what is the current status of support for other interpreted
languages in the Guile VM? For example, what's the status of Python for
Guile? As probably many of you , once I've felt the power of lispy
languages, it's an annoyance to go back to anything inferior, but many
people I work with use "the median language" (in words of P. Graham).
These days, this seems to be python. So, if i'm developing a nice
container for the scientific code i'm developing, i'd like to make this
essentially scheme, but i'd also like to give people a chance to extend
it via the popular language of the hour.


Cheers



-- 
  
  msematman@myopera.com



  parent reply	other threads:[~2013-11-30  9:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 16:00 guile scripting for gdb Doug Evans
2013-11-07 23:39 ` Ludovic Courtès
2013-11-09 18:40   ` Doug Evans
2013-11-09 19:50     ` Thien-Thi Nguyen
2013-11-09 20:33     ` Doug Evans
2013-11-11  0:19     ` Ludovic Courtès
2013-11-11  1:50       ` Doug Evans
2013-11-11  6:28         ` Doug Evans
2013-11-11 11:55           ` Ludovic Courtès
2013-11-11 11:47         ` Ludovic Courtès
2013-11-30  9:15   ` msematman [this message]
2013-12-02  3:49     ` Nala Ginrut
2013-12-02 12:10       ` extending guile programs thru python (or lua, or whatever ...) msematman
  -- strict thread matches above, loose matches on Subject: below --
2013-11-04 15:57 guile scripting for gdb Doug Evans

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=1385802914.11498.53756421.78A1B0B8@webmail.messagingengine.com \
    --to=msematman@myopera.com \
    --cc=guile-user@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).