unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Clinton Ebadi <clinton@unknownlamer.org>
Subject: Extended -e syntax
Date: Sun, 29 Feb 2004 22:32:45 -0500	[thread overview]
Message-ID: <200402292232.51103.clinton@unknownlamer.org> (raw)

[-- Attachment #1: Type: Text/Plain, Size: 1344 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've been trying to get guile-pg to compile and it hasn't been working out too 
well...ttn uses his new build system stuff with guile-pg and they only work 
with Guile 1.4.x unless Guile has support for his extended -e syntax.

As such, I copied ttn's code from Guile 1.4, changed one call (gh_symbol2scm 
into scm_str2symbol), and patched it into Guile CVS HEAD. Is ttn still 
assigning his copyright to the FSF? The copyright notices on all the files 
would make it appear so (I have sent this to guile-user as well as -devel so 
ttn will see it since he unsubscribed from guile-devel after he forked 
Guile).

Is there any chance of mainline Guile using the extended -e stuff or accepting 
patches to use ttn's nice build system and extended guile-config stuff? I am 
willing to chunk out anything from Guile 1.4.x that would be useful to the 
official Guile branch if there aren't any copyright issues / the patches will 
be accepted.
- -- 
http://unknownlamer.org
AIM:unknownlamer IRC:unknown_lamer@freenode#hprog
I use Free Software because I value freedom over features.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAQq7hdgGh8PQDV0sRAgmaAKDOGauT/JB6deQImYK8f26YgzKW2wCfZtCw
0v5EcxFcvfUvhJS6xjyUx6w=
=uCBU
-----END PGP SIGNATURE-----

[-- Attachment #2: extended_e.patch.bz2 --]
[-- Type: application/x-bzip2, Size: 1139 bytes --]

[-- Attachment #3: Type: text/plain, Size: 139 bytes --]

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

             reply	other threads:[~2004-03-01  3:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01  3:32 Clinton Ebadi [this message]
2004-03-01  5:04 ` Extended -e syntax Andreas Rottmann
     [not found]   ` <E1AxlJY-0002cb-00@surf.glug.org>
2004-03-01 14:27     ` Arch and Guile Andreas Rottmann
2004-03-01 19:04       ` ITLA (was Re: Arch and Guile) Tom Lord
2004-03-01 19:14         ` ITLA Andreas Rottmann
2004-03-01 21:55           ` ITLA Tom Lord
2004-03-02  0:11             ` ITLA Andreas Rottmann
2004-03-02  2:50               ` ITLA Tom Lord
2004-03-02 14:04                 ` ITLA Andreas Rottmann
2004-03-02  3:26             ` ITLA Miles Bader
2004-03-03 11:22           ` ITLA Neil Jerram
2004-03-03 11:55             ` ITLA Andreas Rottmann
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
     [not found]   ` <E1AziNk-0007mW-00@surf.glug.org>
2004-03-06 20:39     ` ttn's build system Andreas Rottmann
2004-03-10 18:59   ` Andreas Rottmann
2004-03-10 22:28   ` ttn's build system [was: Extended -e syntax] Clinton Ebadi
2004-03-10 23:22   ` Tom Lord

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=200402292232.51103.clinton@unknownlamer.org \
    --to=clinton@unknownlamer.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).