From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed1.bredband.com!bredband!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: Lisp problems (maybe emacs) Date: 22 Nov 2002 04:14:35 +0000 Organization: Naggum Software, Oslo, Norway Lines: 19 Message-ID: <3246927275072989@naggum.no> References: <87u1ifrsxq.fsf@noetbook.telent.net> <3246865033906081@naggum.no> <3246909790346555@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1037938476 14311 129.240.65.5 (22 Nov 2002 04:14:36 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 22 Nov 2002 04:14:36 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:47383 * Christian Nybø | I've lately seen examples of this relation -- are there papers covering | the subject? I have not seen any papers on it, but those who think about the issue for just a few seconds realize that parsing is a stateful process and regular expressions are inherently stateless and the amount of state information you can thereby employ in the syntax recognition process is very limited. Some of the things I want help with when looking at code is to click on a symbol name and see its lexical scope and all references highlighted, or to show free variable references inside each enclosing scope. Such things are not hard to do if you edit the actual code instead of just characters. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.