() [email protected] (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.
