RE: Change on indent from 2.2.12 to 2.2.13

"De Lara Guarch, Pablo" <[email protected]> Thu, 28 Mar 2024 16:01:11 +0000
Newsgroups gmane.comp.gnu.indent.bugs
Message-ID <DM8PR11MB559142E8750292702D24E63A843B2@DM8PR11MB5591.namprd11.prod.outlook.com>
Hi Simon,

> -----Original Message-----
> From: Simon Josefsson <[email protected]>
> Sent: Wednesday, March 27, 2024 4:31 PM
> To: De Lara Guarch, Pablo <[email protected]>
> Cc: [email protected]
> Subject: Re: Change on indent from 2.2.12 to 2.2.13
>=20
> "De Lara Guarch, Pablo" <[email protected]> writes:
>=20
> > Hello,
> >
> > This is not really a bug on indent, I would say, but I am seeing differ=
ences in
> how C code is indented with 2.2.13 against 2.2.12.
> > With 2.2.12, the code as it is looks OK, but with 2.2.13, it makes the =
following
> change.
> >
> > -uint32_t crc32_gzip_refl_base(uint32_t seed, uint8_t * buf, uint64_t
> > len)
> > +uint32_t crc32_gzip_refl_base(uint32_t seed, uint8_t *buf, uint64_t
> > +len)
> >
> > Is there a way to avoid the 2.2.13 to make this change, so it is compat=
ible with
> 2.2.12 (which is still present in many distros)?
>=20
> FWIW, I've adopted the approach to make this indentation change in the pr=
oject
> I help maintain, because it is arguable fixing a bug, and then say that G=
NU indent
> 2.2.13 is required to re-indent source code, and have updated CI/CD testi=
ng to
> only verify code indentation using 2.2.13.
> Not really an answer to your question, but maybe it will encourage you to=
 adopt
> a similar solution that I have...

Thanks for your reply. Pity that older distros like Ubuntu 22.04 still use =
2.2.12...

Pablo
>=20
> /Simon