home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #19 / NN_1992_19.iso / spool / comp / lang / scheme / 2132 < prev    next >
Encoding:
Text File  |  1992-09-01  |  1.3 KB  |  36 lines
  1. Newsgroups: comp.lang.scheme
  2. Path: sparky!uunet!cs.utexas.edu!sdd.hp.com!apollo.hp.com!netnews
  3. From: sommerfeld@apollo.hp.com (Bill Sommerfeld)
  4. Subject: Re: wots going on here!?
  5. Sender: usenet@apollo.hp.com (Usenet News)
  6. Message-ID: <SOMMERFELD.92Sep1131757@gourmet.apollo.hp.com>
  7. In-Reply-To: jinx@zurich.ai.mit.edu's message of 1 Sep 92 07:30:12 GMT
  8. Date: Tue, 1 Sep 1992 17:17:01 GMT
  9. Lines: 18
  10. References: <17timvINN7b8@agate.berkeley.edu>
  11.     <17tn1uINNkij@early-bird.think.com>
  12.     <JINX.92Aug31170432@chamarti.ai.mit.edu>
  13.     <17ur1oINNem6@agate.berkeley.edu>
  14.     <JINX.92Sep1033012@chamarti.ai.mit.edu>
  15. Nntp-Posting-Host: gourmet.ch.apollo.hp.com
  16. Organization: Hewlett Packard
  17.  
  18. In article <JINX.92Sep1033012@chamarti.ai.mit.edu> jinx@zurich.ai.mit.edu (Guillermo J. Rozas) writes:
  19.  
  20.    A possibility would be to have multiple "unspecified" objects, one for
  21.    IF, one for COND, etc., so the object itself would print something like
  22.  
  23.    "#[unspecified IF alternative]"
  24.  
  25.    which would probably make the error easier to track.
  26.    However, it would probably still be confusing to a beginner.
  27.  
  28. How about
  29.  
  30. "#[unspecified IF alternative at line xxx character yyy of source file zzz.scm]"
  31.  
  32. or some other such reference back to the source code which would point
  33. the beginner right at the bug.
  34.  
  35. These could be generated *once* when reading in the source.
  36.