From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.user Subject: Re: request: libguile to wrap getsid(2) Date: Mon, 28 Dec 2009 13:18:30 +0100 Message-ID: <87637re1gp.fsf@ambire.localdomain> References: <87ws09y3g3.fsf@ambire.localdomain> <87pr601t5c.fsf@ossau.uklinux.net> <877hs8xbwi.fsf@ambire.localdomain> <878wcnfj5k.fsf@ossau.uklinux.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1262003006 13934 80.91.229.12 (28 Dec 2009 12:23:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Dec 2009 12:23:26 +0000 (UTC) To: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Dec 28 13:23:19 2009 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NPEd4-00039B-Rm for guile-user@m.gmane.org; Mon, 28 Dec 2009 13:23:19 +0100 Original-Received: from localhost ([127.0.0.1]:53880 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPEd5-0003u5-1b for guile-user@m.gmane.org; Mon, 28 Dec 2009 07:23:19 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPEcz-0003t7-Pr for guile-user@gnu.org; Mon, 28 Dec 2009 07:23:13 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPEct-0003qA-KJ for guile-user@gnu.org; Mon, 28 Dec 2009 07:23:13 -0500 Original-Received: from [199.232.76.173] (port=35031 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPEct-0003q5-BT for guile-user@gnu.org; Mon, 28 Dec 2009 07:23:07 -0500 Original-Received: from smtp-out01.alice.it ([85.33.2.12]:1075) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NPEcs-00058p-Hw for guile-user@gnu.org; Mon, 28 Dec 2009 07:23:07 -0500 Original-Received: from fbcmmo06.fbc.local ([192.168.184.137]) by smtp-out01.alice.it with Microsoft SMTPSVC(6.0.3790.3959); Mon, 28 Dec 2009 13:23:04 +0100 Original-Received: from FBCMCL01B09.fbc.local ([192.168.171.26]) by fbcmmo06.fbc.local with Microsoft SMTPSVC(6.0.3790.3959); Mon, 28 Dec 2009 13:20:47 +0100 Original-Received: from ambire.localdomain ([79.45.74.23]) by FBCMCL01B09.fbc.local with Microsoft SMTPSVC(6.0.3790.3959); Mon, 28 Dec 2009 13:20:47 +0100 Original-Received: from ttn by ambire.localdomain with local (Exim 4.63) (envelope-from ) id 1NPEYR-0005jG-1h for guile-user@gnu.org; Mon, 28 Dec 2009 13:18:31 +0100 In-Reply-To: <878wcnfj5k.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon, 28 Dec 2009 11:11:03 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-OriginalArrivalTime: 28 Dec 2009 12:20:47.0511 (UTC) FILETIME=[2F8EF270:01CA87B8] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:7584 Archived-At: () Neil Jerram () Mon, 28 Dec 2009 11:11:03 +0000 recasting at runtime [...] also supports writing out recast code - although perhaps at the cost of losing some formatting and comments. A good start! In my mind, the formatting and comments are part of the essence. Can you give an example of what grok-db might say? I envision grok-db not as program, but a data structure (database). As such, the compiler (and other tools) would add/update/zonk bits of knowledge in the form of: (ID GIVEN RESULT...) tuples, where GIVEN may be one of: ID ; reference LOCATION (LOCATION CONTEXT) where LOCATION is some (FILENAME FORM-NODE-ID ETC...) form; CONTEXT is (STATIC [DYNAMIC...]); and RESULT is something that the compiler can use in its transforms. Also note that grok-db is in a sense already present, in the source code of the compiler. Exactly. We want to teach the compiler to share its thoughts, and perhaps learn from the thoughts of others. If the programmer (or other tool) has insight that the compiler lacks, there is no reason to deny it access. Obviously, it goes the other way, too! thi