From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: byte compiling defcustom Date: Mon, 19 Nov 2007 14:03:18 -0500 Message-ID: References: <200711171647.lAHGlHqH024027@jane.dms.auburn.edu> <200711172032.lAHKWhgx025030@jane.dms.auburn.edu> <200711172041.lAHKf2SG025058@jane.dms.auburn.edu> <200711180413.lAI4DLF8025958@jane.dms.auburn.edu> <200711181841.lAIIfDB2028254@jane.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1195499331 31368 80.91.229.12 (19 Nov 2007 19:08:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 19 Nov 2007 19:08:51 +0000 (UTC) Cc: teirllm@dms.auburn.edu, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 19 20:08:47 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IuByQ-0007i6-VV for ged-emacs-devel@m.gmane.org; Mon, 19 Nov 2007 20:07:59 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IuByD-00073Q-E3 for ged-emacs-devel@m.gmane.org; Mon, 19 Nov 2007 14:07:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IuBty-0004IX-Bg for emacs-devel@gnu.org; Mon, 19 Nov 2007 14:03:22 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IuBtv-0004F5-L0 for emacs-devel@gnu.org; Mon, 19 Nov 2007 14:03:20 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IuBtv-0004Ed-D9 for emacs-devel@gnu.org; Mon, 19 Nov 2007 14:03:19 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IuBtu-0003zU-Sw for emacs-devel@gnu.org; Mon, 19 Nov 2007 14:03:19 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1IuBtu-0005rf-IX; Mon, 19 Nov 2007 14:03:18 -0500 In-reply-to: (message from Dan Nicolaescu on Sun, 18 Nov 2007 15:29:25 -0800) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:83681 Archived-At: Again, I claim that if the user needs to see lisp for a defcustom, then the defcustom is not designed well enough and is not very user friendly. That may be true to some extent, but I am not sure it is always true. Anyway these defcustoms shuld work right even if their definitions are not ideal. To me it seems that maintaining an infrastructure to access the original lisp values for defcustom is just added complexity It is reduced complexity. The code to compile these values would be added complexity.