From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!tank.news.pipex.net!pipex!newsfeed.esat.net!nslave.kpnqwest.net!nloc1.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Context of macro call References: <87wuz1jipx.fsf@photino.sid.rice.edu> Mail-Copies-To: never From: Erik Naggum Message-ID: <3218960368973315@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Jan 2002 11:39:30 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader3.kpnqwest.net 1009971570 193.71.66.49 (Wed, 02 Jan 2002 12:39:30 MET) NNTP-Posting-Date: Wed, 02 Jan 2002 12:39:30 MET Xref: archiver1.google.com comp.lang.lisp:23476 * cubicle584@mailandnews.com (Software Scavenger) | ERROR is how we give the user an error message. But that error message | has to say something. In the case of incorrect macro arguments, it | should say what those macro arguments were, why they were wrong, and | where they are in the program. The question is how the macro knows where | it was called, so it can make that information part of the error message. Would not the compiler know this and make it part of its error message? /// --