Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compilers > #3426
| From | Spiros Bousbouras <spibou@gmail.com> |
|---|---|
| Newsgroups | comp.compilers |
| Subject | Re: A simpler way to tokenize and parse? |
| Date | 2023-03-26 14:10 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <23-03-024@comp.compilers> (permalink) |
| References | <23-03-011@comp.compilers> <23-03-019@comp.compilers> |
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 .
Back to comp.compilers | Previous | Next — Previous in thread | Next in thread | Find similar
A simpler way to tokenize and parse? Roger L Costello <costello@mitre.org> - 2023-03-24 14:45 +0000
Re: Lisp syntax, was A simpler way to tokenize and parse? Spiros Bousbouras <spibou@gmail.com> - 2023-03-25 11:55 +0000
Re: Lisp syntax, was A simpler way to tokenize and parse? gah4 <gah4@u.washington.edu> - 2023-03-25 14:32 -0700
Re: Lisp syntax, was A simpler way to tokenize and parse? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2023-03-25 13:14 +0000
Re: Lisp syntax, was A simpler way to tokenize and parse? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-03-26 00:46 +0000
Re: A simpler way to tokenize and parse? Lieven Marchand <mal@wyrd.be> - 2023-03-25 19:58 +0100
Re: A simpler way to tokenize and parse? Spiros Bousbouras <spibou@gmail.com> - 2023-03-26 14:10 +0000
Re: A simpler way to tokenize and parse? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-03-26 18:19 +0000
Re: Lisp syntax, A simpler way to tokenize and parse? Lieven Marchand <mal@wyrd.be> - 2023-03-27 23:15 +0200
Re: A simpler way to tokenize and parse? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-03-26 01:17 +0000
csiph-web