Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| A simpler way to tokenize and parse? costello@mitre.org (Roger L Costello) (2023-03-24) |
| Re: A simpler way to tokenize and parse? mal@wyrd.be (Lieven Marchand) (2023-03-25) |
| Re: A simpler way to tokenize and parse? 864-117-4973@kylheku.com (Kaz Kylheku) (2023-03-26) |
| Re: A simpler way to tokenize and parse? spibou@gmail.com (Spiros Bousbouras) (2023-03-26) |
| Re: A simpler way to tokenize and parse? christopher.f.clark@compiler-resources.com (Christopher F Clark) (2023-03-26) |
| Re: A simpler way to tokenize and parse? 864-117-4973@kylheku.com (Kaz Kylheku) (2023-03-26) |
| Re: A simpler way to tokenize and parse? tkoenig@netcologne.de (Thomas Koenig) (2023-03-27) |
| From: | Spiros Bousbouras <spibou@gmail.com> |
| Newsgroups: | comp.compilers |
| Date: | Sun, 26 Mar 2023 14:10:14 -0000 (UTC) |
| Organization: | A noiseless patient Spider |
| References: | 23-03-011 23-03-019 |
| 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-Organisation: | Weyland-Yutani |
| In-Reply-To: | 23-03-019 |
On Sat, 25 Mar 2023 19:58:58 +0100
Lieven Marchand <mal@wyrd.be> 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 .
Return to the
comp.compilers page.
Search the
comp.compilers archives again.