From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Stefan Monnier" Newsgroups: gmane.emacs.help Subject: Re: Using custom as a type checker:- ramble Date: 27 Mar 2003 11:32:33 -0500 Organization: Yale University Sender: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <5lr88s93dq.fsf@rum.cs.yale.edu> References: <5ld6ke9k6c.fsf@rum.cs.yale.edu> <5l4r5q9bzx.fsf@rum.cs.yale.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1048783425 5397 80.91.224.249 (27 Mar 2003 16:43:45 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 27 Mar 2003 16:43:45 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Thu Mar 27 17:43:44 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18yaTO-0001Nh-00 for ; Thu, 27 Mar 2003 17:43:26 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18yaQY-000541-01 for gnu-help-gnu-emacs@m.gmane.org; Thu, 27 Mar 2003 11:40:30 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!logbridge.uoregon.edu!news.ycc.yale.edu!rum.cs.yale.edu!rum.cs.yale.edu Original-Newsgroups: gnu.emacs.help Original-Lines: 22 Original-NNTP-Posting-Host: rum.cs.yale.edu User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Original-NNTP-Posting-Host: rum.cs.yale.edu X-Original-Trace: 27 Mar 2003 11:32:33 -0500, rum.cs.yale.edu Original-Xref: shelby.stanford.edu gnu.emacs.help:111453 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:7953 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:7953 Stefan> It should be possible to get the desired result without Stefan> implementing an elisp interpreter in elisp, but instead by Stefan> temporarily rebinding `setq' as a macro (and things like Stefan> that). > I think that would be fairly hard! setq is such a basic function, and > to change it so that it worked correctly, but still failed at the > appropriate time. I don't intend it to fail any more than the plain `setq' does. The only difference would be a bunch of warnings. > I presume you are still suggesting using the type information in > custom to make the determination as to whether an .emacs setq was > "type safe" or not? If this is the case, it would seem the two > approaches (a custom-setq, or augmented setq) would use a lot of > common code. Probably, but without making it visible at the source level and without impacting the semantics of the code at all. Stefan