Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!border-4.nntp.ord.giganews.com!border-1.nntp.ord.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Kaz Kylheku <643-408-1753@kylheku.com> Newsgroups: comp.compilers Subject: Re: paper: Towards Automatic Error Recovery in Parsing Expression Date: Wed, 09 Jul 2025 04:33:43 -0000 Organization: Compilers Central Sender: johnl%iecc.com Approved: comp.compilers@iecc.com Message-ID: <25-07-005@comp.compilers> References: <25-07-004@comp.compilers> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="10094"; mail-complaints-to="abuse@iecc.com" Keywords: errors, parse, comment Posted-Date: 10 Jul 2025 14:56:32 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Lines: 26 Xref: csiph.com comp.compilers:3672 On 2025-07-09, John R Levine quoted: > Error recovery is an essential feature for a parser that should be plugged > in Integrated Development Environments (IDEs), which must build Abstract I am deeply skeptical. Error recovery is essential when you're handing a deck of punched cards to a job submission window. A compiler integrated into an IDE can stop at the first error, put the cursor there and so it goes. The IDE can always be compiling as you type each character, so that most of the time there are no errors in the code. The only time an error occurs is when you type something malformed or not yet complete, and that is happening exactly in one place: where the cursor is in the file that has the current editing focus. The situation is flagged as you type so you fix it If your refactoring tools are producing bad code, the tools need to be repaired. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca [It's a little more complicated than that. Sometimes you cut and paste code, or you import a file of code from somewhere. But I agree that a plausible approach is to stop at the first error and say fix it. -John]