unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Phillip Lord <p.lord@russet.org.uk>
Subject: Re: Using custom as a type checker:- ramble
Date: 27 Mar 2003 10:25:50 +0000	[thread overview]
Message-ID: <vf3cl9umvl.fsf@rpc71.cs.man.ac.uk> (raw)
In-Reply-To: 5l4r5q9bzx.fsf@rum.cs.yale.edu

>>>>> "Stefan" == Stefan Monnier <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> writes:

  >> > I.e. I don't want to change the .emacs code at all, but I'd
  >> > like
  >> >to have a more-or-less generic way to add helpful analysis of
  >> >the code so as to give useful information to the user about
  >> >suspicious customizations.

  >> Well I would agree that this would be preferable.

  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 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. 




  Stefan> Another alternative is to put the checking into the
  Stefan> byte-compiler (which already takes care of traversing elisp
  Stefan> code) and then byte-compile the .emacs file (not for speed
  Stefan> but for sanity checks).  This might be the best option.

That also sounds plausible, if somewhat beyond my elisp coding
skills. 


Cheers

Phil

  reply	other threads:[~2003-03-27 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 18:22 Using custom as a type checker:- ramble Phillip Lord
2003-03-26 16:17 ` Stefan Monnier
2003-03-26 16:59   ` Phillip Lord
2003-03-26 19:14     ` Stefan Monnier
2003-03-27 10:25       ` Phillip Lord [this message]
2003-03-27 16:32         ` Stefan Monnier
2003-03-27 17:11           ` Phillip Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vf3cl9umvl.fsf@rpc71.cs.man.ac.uk \
    --to=p.lord@russet.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).