Path: csiph.com!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Spiros Bousbouras Newsgroups: comp.compilers Subject: Re: A simpler way to tokenize and parse? Date: Sun, 26 Mar 2023 14:10:14 -0000 (UTC) Organization: A noiseless patient Spider Sender: johnl@iecc.com Approved: comp.compilers@iecc.com Message-ID: <23-03-024@comp.compilers> References: <23-03-011@comp.compilers> <23-03-019@comp.compilers> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="3002"; mail-complaints-to="abuse@iecc.com" Keywords: Lisp, syntax Posted-Date: 26 Mar 2023 20:46:31 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com X-Organisation: Weyland-Yutani In-Reply-To: <23-03-019@comp.compilers> Xref: csiph.com comp.compilers:3426 On Sat, 25 Mar 2023 19:58:58 +0100 Lieven Marchand wrote: > Apart from the already mentioned problem that it forces you into a > syntax that a lot of people don't like, there's also the problem that > you have to deal with hostile input. Where you expect "(+ 2 3)" someone > will enter "(+ 2 3 #.(progn (launch-the-nukes) 4))". The ability to read S-expressions does not imply that you must also have a "read and evaluate" facility. In any case , in Common Lisp you can trivially disable it by setting *READ-EVAL* to NIL .