From: Alexis <flexibeast@gmail.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Unix Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: A fuzzy awk.
Date: Wed, 22 May 2024 15:08:29 +1000 [thread overview]
Message-ID: <875xv6bfhu.fsf@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2405221325100.15285@aneurin.horsfall.org> (Dave Horsfall's message of "Wed, 22 May 2024 13:26:36 +1000 (EST)")
Dave Horsfall <dave@horsfall.org> writes:
> On Tue, 21 May 2024, Paul Winalski wrote:
>
>> To take an example that really happened, a fuzz test consisting
>> of 100
>> nested parentheses caused an overflow in a parser table (it
>> could only
>> handle 50 nested parens). Is that worth fixing?
>
> Well, they could be a rabid LISP programmer...
Just did a quick check of some of the ELisp packages on my system:
* For my own packages, the maximum was 10 closing parentheses.
* For the packages in my elpa/ directory, the maximum was 26 in
ducpel-glyphs.el, where they were part of a glyph, rather than
delimiting code. The next highest value was 16, in org.el and
magit-sequence.el.
i would suggest that any Lisp with more than a couple of dozen
closing parentheses is in dire need of refactoring. Although of
course someone who's rabid is probably not in the appropriate
mental state for that. :-)
Alexis.
next prev parent reply other threads:[~2024-05-22 5:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 14:09 Serissa
2024-05-21 1:56 ` Rob Pike
2024-05-21 2:47 ` Larry McVoy
2024-05-21 2:54 ` Lawrence Stewart
2024-05-21 3:36 ` Rob Pike
2024-05-21 11:59 ` Peter Weinberger (温博格) via TUHS
2024-05-21 3:53 ` George Michaelson
2024-05-21 16:59 ` Paul Winalski
2024-05-21 17:56 ` segaloco via TUHS
2024-05-21 18:12 ` Luther Johnson
2024-05-22 15:37 ` Paul Winalski
2024-05-22 18:49 ` Larry McVoy
2024-05-22 20:17 ` Larry McVoy
2024-05-22 3:26 ` Dave Horsfall
2024-05-22 5:08 ` Alexis [this message]
2024-05-22 13:12 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2024-05-23 13:49 Douglas McIlroy
2024-05-23 20:52 ` Rob Pike
2024-05-24 5:41 ` andrew
2024-05-24 7:17 ` Ralph Corderoy
2024-05-24 7:41 ` Rob Pike
2024-05-24 11:56 ` Dan Halbert
2024-05-25 0:17 ` Bakul Shah via TUHS
2024-05-25 0:57 ` G. Branden Robinson
2024-05-25 13:56 ` David Arnold
2024-05-25 17:18 ` Paul Winalski
2024-05-25 17:36 ` Tom Perrine
2024-05-20 13:06 [TUHS] A fuzzy awk. (Was: The 'usage: ...' message.) Douglas McIlroy
2024-05-20 13:25 ` [TUHS] " Chet Ramey
2024-05-20 13:41 ` [TUHS] Re: A fuzzy awk Ralph Corderoy
2024-05-20 14:26 ` Chet Ramey
2024-05-22 13:44 ` arnold
2024-05-20 13:54 ` Ralph Corderoy
2024-05-19 23:08 [TUHS] The 'usage: ...' message. (Was: On Bloat...) Douglas McIlroy
2024-05-20 0:58 ` [TUHS] " Rob Pike
2024-05-20 3:19 ` arnold
2024-05-20 9:20 ` [TUHS] A fuzzy awk. (Was: The 'usage: ...' message.) Ralph Corderoy
2024-05-20 13:10 ` [TUHS] " Chet Ramey
2024-05-20 13:30 ` [TUHS] Re: A fuzzy awk Ralph Corderoy
2024-05-20 13:48 ` Chet Ramey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xv6bfhu.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).