GNU bug report logs - #56393
Actually fix the long lines display bug

Previous Next

Full log

Message #272 received at 56393 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: gregory <at> heytings.org
Cc: gerd.moellmann <at> gmail.com, larsi <at> gnus.org, 56393 <at> debbugs.gnu.org
Subject: Re: bug#56393: Actually fix the long lines display bug
Date: Sat, 09 Jul 2022 12:30:05 +0300

> Cc: gerd.moellmann <at> gmail.com, larsi <at> gnus.org, 56393 <at> debbugs.gnu.org
> Date: Sat, 09 Jul 2022 12:20:38 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > > . The WITH_NARROWED_BEGV macro is IMO awkward and not very convenient to 
> > > use in C.  For starters, it cannot accommodate multi-line code, except 
> > > via the 'do { ... } while(0);' kludge, which I think will make the code 
> > > less readable.  It also should set up an unwind-protect handler, so that 
> > > any non-local exit from the code will restore BEGV/ZV.  So I think it 
> > > will be better to have two separate functions (and a third one to 
> > > unwind).
> > >
> > 
> > Hmmm...  I'll see what I can do.  (But I don't understand why you write 
> > that it cannot accomodate multi-line code: you can write 
> > "WITH_NARROWED_BEGV (frobnicate (foo); frobnicate (bar));".)
> 
> What if the multi-line code includes an if clause or a for loop with
> just one line in their bodies?

This also requires to remember NOT to use a semi-colon at the end of
the last line, which is problematic.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.