From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-user@gnu.org
Subject: Re: RPX 1.0 available
Date: Thu, 07 Jan 2010 11:18:41 +0100 [thread overview]
Message-ID: <87k4vumd4u.fsf@ambire.localdomain> (raw)
In-Reply-To: <87wrzvy22p.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 06 Jan 2010 11:12:14 +0100")
() ludo@gnu.org (Ludovic Courtès)
() Wed, 06 Jan 2010 11:12:14 +0100
Hello!
Greetings!
Excellent, and nice to see it’s 100% Scheme code!
Well, as you can see, *which* 100% is still a question...
I’m looking forward for the 1.9/2.0 port. :-)
Me too.
Currently ‘ttn-do’ fails to build for me with 1.9:
ERROR: In procedure module-variable:
ERROR: Wrong type argument in position 1 (expecting module): #f
ERROR: In procedure module-variable:
ERROR: Wrong type argument in position 1 (expecting module): #f
Thanks for reporting this. I don't expect to address this problem
specifically; perhaps it will sort itself out in the scheduled general
revamping of ttn-do (you can monitor its NEWS for "tested with Guile
1.9").
BTW, what would you think of releasing the X11-related part of
‘ttn-do’ as a standalone library?
I'd rather get all of ttn-do to be Guile 1.9 hostable, then do the
split. I think that would be most expedient. On the other hand, the
X11-related parts could do with some re-design -- both interface and
internals -- and that might benefit from early separation. More modular
requires more communication (between programmers, the code itself, and
client code), which is a struggle for old frogs like me, but seems to be
like water to you tadpoles. Hmmm, we'll see...
Should read: http://www.gnuvola.org/software/rpx/ .
Good catch; thanks.
thi
next prev parent reply other threads:[~2010-01-07 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 1:22 RPX 1.0 available Thien-Thi Nguyen
2010-01-06 10:12 ` Ludovic Courtès
2010-01-07 10:18 ` Thien-Thi Nguyen [this message]
2010-01-11 22:05 ` Ludovic Courtès
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=87k4vumd4u.fsf@ambire.localdomain \
--to=ttn@gnuvola.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).