From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: Installing scheme only programs
Date: Sun, 13 Mar 2011 01:59:17 +0100 [thread overview]
Message-ID: <87wrk325ui.fsf@ambire.localdomain> (raw)
In-Reply-To: <87d3lxom26.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 11 Mar 2011 13:53:37 +0100")
() ludo@gnu.org (Ludovic Courtès)
() Fri, 11 Mar 2011 13:53:37 +0100
But then doesn’t it prevent code reuse?
I don’t know to what extent this applies to RPX, but for instance, you
can’t just ‘(use-modules (rpx the-feature-you-want-to-use))’; you end up
doing ‘(use-modules (rpx))’ and potentially pulling more code than you
really want.
RPX is a program, not a library. The modules it uses can be used by other
programs, certainly. The other RPX-specific functionality should ideally be
split out (librarified) into their own modules for easier code reuse, i agree.
So far, no one has expressed interest, so reality trumps theory for now.
prev parent reply other threads:[~2011-03-13 0:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 6:50 Installing scheme only programs Diogo F. S. Ramos
2011-03-10 9:57 ` Tristan Colgate-McFarlane
2011-03-10 17:42 ` Diogo F. S. Ramos
2011-03-10 10:34 ` Thien-Thi Nguyen
2011-03-10 17:46 ` Diogo F. S. Ramos
2011-03-11 2:18 ` nalaginrut
2011-03-11 4:50 ` dsmich
2011-03-11 4:57 ` Diogo F. S. Ramos
2011-03-11 5:24 ` nalaginrut
2011-03-11 9:16 ` Thien-Thi Nguyen
2011-03-11 12:53 ` Ludovic Courtès
2011-03-13 0:59 ` Thien-Thi Nguyen [this message]
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=87wrk325ui.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=ludo@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).