home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!snorkelwacker.mit.edu!ai-lab!zurich.ai.mit.edu!jinx
- From: jinx@zurich.ai.mit.edu (Guillermo J. Rozas)
- Newsgroups: comp.lang.scheme
- Subject: Re: wots going on here!?
- Message-ID: <JINX.92Sep1211605@rolex.ai.mit.edu>
- Date: 2 Sep 92 01:16:05 GMT
- References: <17timvINN7b8@agate.berkeley.edu> <17tn1uINNkij@early-bird.think.com>
- <JINX.92Aug31170432@chamarti.ai.mit.edu>
- <17ur1oINNem6@agate.berkeley.edu>
- <JINX.92Sep1033012@chamarti.ai.mit.edu>
- <SOMMERFELD.92Sep1131757@gourmet.apollo.hp.com>
- Sender: news@ai.mit.edu
- Reply-To: jinx@zurich.ai.mit.edu
- Organization: M.I.T. Artificial Intelligence Lab.
- Lines: 23
- In-reply-to: sommerfeld@apollo.hp.com's message of 1 Sep 92 17:17:01 GMT
-
- In article <SOMMERFELD.92Sep1131757@gourmet.apollo.hp.com> sommerfeld@apollo.hp.com (Bill Sommerfeld) writes:
-
- | How about
- |
- | "#[unspecified IF alternative at line xxx character yyy of source file zzz.scm]"
- |
- | or some other such reference back to the source code which would point
- | the beginner right at the bug.
- |
- | These could be generated *once* when reading in the source.
- |
-
- That's a nice idea, but I don't like line or character positions, and
- they don't generalize very well to expressions typed at top-level,
- generated by macro expansion, or given to EVAL as arguments.
-
- It also means that the code (and system) grows because of all such
- objects to be tracked, so I don't think it would be desirable in
- practice.
-
- Given that the debugger can usually provide this information without
- much effort, it hardly seems worthwhile for "regular" users, but is
- probably something worth considering for novices.
-