GNU bug report logs - #56641
Deprecate `lsh`

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: mattiase <at> acm.org, stefankangas <at> gmail.com, 56641 <at> debbugs.gnu.org
Subject: Re: bug#56641: Deprecate `lsh`
Date: Wed, 20 Jul 2022 14:24:50 +0300

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: stefankangas <at> gmail.com,  mattiase <at> acm.org,  56641 <at> debbugs.gnu.org
> Date: Wed, 20 Jul 2022 11:20:14 +0800
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > If it's rare enough (as it should be), I don't see the annoyance.  Am
> > I missing something?
> 
> It might be rare, but there's nothing wrong with using lsh for its
> intended purpose, which is handling negative numbers correctly in
> several different situations.

The point is that people could use lsh because they don't realize they
could use ash instead.  If one really must use lsh, there's always
with-no-warnings, which is IMO fine for the rare situations where it's
needed.

> Byte-compiler warnings are supposed to point out problems.

And this could indeed be a problem: that the programmer is not aware
of a better alternative.

So I don't see a problem with warning in this case, I just don't want
us to pretend this function is "obsolete", because it isn't.

Previous Next

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