From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: Re: [9front] Bug in rc
Date: Wed, 26 Apr 2023 19:15:08 -0700 [thread overview]
Message-ID: <ZEnarA5Md27UlBVO@alice> (raw)
In-Reply-To: <7BAAF1BDE05AF95E8E1167B980AD0CDA@eigenstate.org>
ori@eigenstate.org once said:
> Quoth Yury Chumak <sfynkx@gmail.com>:
> > Hello all..
> >
> > Noticed that rc returns error 'stack overflow' if code consists
> > 'switch' construction with big amount of 'case' blocks. Steps to
> > reproduce:
>
> [...]
>
> But I'm not sure why it matters; you can hit a
> limit with a huge switch, but it doesn't seem
> like a limit for practical code.
I agree with Ori. If you actually need a workaround,
increase YYMAXDEPTH in /sys/src/cmd/rc/rc.h and
recompile.
Cheers,
Anthony
next prev parent reply other threads:[~2023-04-27 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 18:20 Yury Chumak
2023-04-27 0:44 ` ori
2023-04-27 2:05 ` Yury Chumak
2023-04-27 2:15 ` Anthony Martin [this message]
2023-04-27 3:09 ` Yury Chumak
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=ZEnarA5Md27UlBVO@alice \
--to=ality@pbrane.org \
--cc=9front@9front.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).