From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.user Subject: Re: language translator help Date: Sat, 18 May 2002 19:32:39 -0700 Sender: guile-user-admin@gnu.org Message-ID: References: <15561.38014.967466.255795@segfault.bogus.domain> <15563.18078.788420.299836@segfault.bogus.domain> <87ofg4zkhp.fsf@becket.becket.net> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1021776156 26818 127.0.0.1 (19 May 2002 02:42:36 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 19 May 2002 02:42:36 +0000 (UTC) Cc: guile-user@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 179Gea-0006yR-00 for ; Sun, 19 May 2002 04:42:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 179GbA-0004XH-00; Sat, 18 May 2002 22:39:04 -0400 Original-Received: from ca-crlsbd-u5-c4a-a-172.crlsca.adelphia.net ([24.48.214.172] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 179GYs-0004J7-00 for ; Sat, 18 May 2002 22:36:43 -0400 Original-Received: from ttn by giblet with local (Exim 3.35 #1 (Debian)) id 179GUx-0005fg-00; Sat, 18 May 2002 19:32:39 -0700 Original-To: neil@ossau.uklinux.net In-Reply-To: (message from Neil Jerram on 18 May 2002 14:47:24 +0100) Errors-To: guile-user-admin@gnu.org X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.user:457 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:457 From: Neil Jerram Date: 18 May 2002 14:47:24 +0100 BTW, is there any reason not to sync guile-lang-allover back up with the guile-rgx-ctax module? not in this case. the changes are mostly documentation (adding README), style adaptations (using parens for module names instead of something #/like/this), and similar packaging.[1] thi> in the process, libguilereadline and libqthreads will also be thi> moved to $prefix/lib/guile/1.4.2 -- the only thing in thi> $prefix/lib will be libguile -- and scheme bindings to lt_* thi> will be introduced (where it makes sense). this allows thi> `load-extension' and ilk implementation experimentation. On this point I'd really like to see consensus (w.r.t. 1.6.x and 1.8.x plans) before you proceed. this is why there is TODO item "write $w/modules/compiled-modules.text". it's easy to avoid consensus through m.l. rehash. w/ something written down, the design and its decisions can be thoroughly vetted (which helps build consensus). for lt_* bindings availability, the way to judge that is to ask if lt_* interface is stable. thi> 1.4.2 also back-ports :select and :renamer [...], thi> [...] first module built suchly will be guile-doc-snarf is it perhaps the case that you are only able to do this because you're running with 1.4.x on your own and with hindsight? i don't know how to answer this. what is hindsight to some is foresight to others. project development train-wreck is easy to predict for the switch-yard controller but perhaps not for the passenger, conductor or engineer. it all depends on your relationship w/ the train(s) and of course experience. In other words, do you think a similarly planned model could apply to bleeding edge development? this is another question entirely! bleeding edge doesn't usually tolerate planning but for bleeding edge to stop bleeding, its fruits must be served w/ the wine of planning, else the meal is unpalatable. what makes a good wine? what this means is that if you are project manager at war against time the enemy, you form both a forward flank and a rear guard, and structure communication between these groups to be subject to moderation by the generals back at HQ. what makes a good general? I don't see how you will achieve consensus on 1.4.x directions without being subscribed to guile-devel. So this is a bit too confrontational for my liking. it is my way of retiring to the rear guard, where at least one principle is clear (maintain compatibility). i don't expect forward flank to value these efforts. thi _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://mail.gnu.org/mailman/listinfo/guile-user