unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Patches from ttn's tree to Guile CVS
Date: Tue, 09 Mar 2004 21:36:28 +0100	[thread overview]
Message-ID: <87znap7o6r.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200403032038.07053.clinton@unknownlamer.org> (Clinton Ebadi's message of "Wed, 3 Mar 2004 20:37:53 -0500")

Clinton Ebadi <clinton@unknownlamer.org> writes:

> Is there any chance of these ever being merged?

About the extended_e.patch.bz2: Guile CVS has a similar mechanism
(inspired by ttn's extended '-e' option).  I find this way of doing
things cleaner since we now have a single way to directly refer to
variables in their modules.

The 'design discussion' (cough) starts here:

  http://mail.gnu.org/archive/html/guile-devel/2003-11/msg00050.html

Also see the thread at

  http://mail.gnu.org/archive/html/guile-user/2003-10/msg00002.html

Excerpt from NEWS:

    ** The '-e' option now 'read's its argument.

    This is to allow the new '(@ MODULE-NAME VARIABLE-NAME)' construct to
    be used with '-e'.  For example, you can now write a script like

      #! /bin/sh
      exec guile -e '(@ (demo) main)' -s "$0" "$@"
      !#

      (define-module (demo)
        :export (main))

      (define (main args)
        (format #t "Demo: ~a~%" args))


    * Changes to Scheme functions and syntax

    ** New syntax '@' and '@@':

    You can now directly refer to variables exported from a module by
    writing

        (@ MODULE-NAME VARIABLE-NAME)

    For example (@ (ice-9 pretty-print) pretty-print) will directly access
    the pretty-print variable exported from the (ice-9 pretty-print)
    module.  You don't need to 'use' that module first.  You can also use
    '@' with 'set!'.

    The related syntax (@@ MODULE-NAME VARIABLE-NAME) works just like '@',
    but it can also access variables that have not been exported.  It is
    intended only for kluges and temporary fixes and for debugging, not
    for ordinary code.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  parent reply	other threads:[~2004-03-09 20:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  1:37 Patches from ttn's tree to Guile CVS Clinton Ebadi
2004-03-06 15:57 ` Neil Jerram
2004-03-10 23:46   ` Marius Vollmer
2004-03-14 10:44     ` Andreas Rottmann
2004-03-21  2:11       ` Marius Vollmer
2004-03-06 17:17 ` guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS] Andreas Rottmann
2004-03-10 22:34   ` Clinton Ebadi
2004-03-12  9:31     ` guile-core in Arch archive Andreas Rottmann
2004-03-10 23:32   ` guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS] Tom Lord
2004-03-06 20:01 ` Patches from ttn's tree to Guile CVS Thamer Al-Harbash
2004-03-07 11:04 ` Marius Vollmer
2004-03-09 20:35 ` Marius Vollmer
2004-03-09 20:36 ` Marius Vollmer [this message]
2004-03-09 20:42 ` Marius Vollmer

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=87znap7o6r.fsf@zagadka.ping.de \
    --to=mvo@zagadka.de \
    --cc=guile-devel@gnu.org \
    --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).