unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: rixed@happyleptic.org
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Trying guile as an extention language for a 'real world' product
Date: Mon, 05 Jul 2010 11:08:29 +0200	[thread overview]
Message-ID: <874ogepa7m.fsf@ambire.localdomain> (raw)
In-Reply-To: <20100703053651.GA13073@yeeloong> (rixed@happyleptic.org's message of "Sat, 3 Jul 2010 07:36:51 +0200")

() rixed@happyleptic.org
() Sat, 3 Jul 2010 07:36:51 +0200

   Are there any contraindication against using
   guile as an extention language for configuration ?

I don't think so.

Configuration is specialization, moved early.
Guile can handle that, as long as early is not too early.

thi



  parent reply	other threads:[~2010-07-05  9:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03  5:36 Trying guile as an extention language for a 'real world' product rixed
2010-07-03 20:31 ` Linas Vepstas
2010-07-03 22:34 ` Ludovic Courtès
2010-07-05  9:08 ` Thien-Thi Nguyen [this message]
2010-07-08 10:45 ` 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=874ogepa7m.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-user@gnu.org \
    --cc=rixed@happyleptic.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).