Hi,
On 08/10/2024 21:55, Gavin Smith wrote:
>
> Yes the locale.h file (generated from locale.in.h) should not exist
> on release/7.1. locale.in.h is tracked in git but locale.h is not so
> is not removed by "git switch". I'll have to find some way of deleting
> this file and others when I switch
On Tue, Oct 08, 2024 at 08:55:30PM +0100, Gavin Smith wrote:
> On Tue, Oct 08, 2024 at 09:23:37PM +0200, Patrice Dumas wrote:
> > On Tue, Oct 08, 2024 at 08:13:12PM +0100, Gavin Smith wrote:
> > > It could only be because I switched from the master branch and there
> > > is something left over from
On Tue, Oct 08, 2024 at 09:23:37PM +0200, Patrice Dumas wrote:
> On Tue, Oct 08, 2024 at 08:13:12PM +0100, Gavin Smith wrote:
> > It could only be because I switched from the master branch and there
> > is something left over from building from the master branch.
>
> ALl the more likely that the g
On Tue, Oct 08, 2024 at 08:13:12PM +0100, Gavin Smith wrote:
> It could only be because I switched from the master branch and there
> is something left over from building from the master branch.
ALl the more likely that the gnulib versions of 7.1 and master are
probably substantially different now
On Sun, Oct 06, 2024 at 01:33:03PM +0200, Patrice Dumas wrote:
> On Sat, Oct 05, 2024 at 11:22:06AM -0600, arn...@skeeve.com wrote:
> > Hi.
> >
> > Apologies for the delay in replying, I've been offline for several
> > days.
> >
> > Thank you for the report. I have fixed all the cases in the manu
Am 08.10.2024 um 01:46 schrieb Patrice Dumas:
However, there is a risk to go through 0 if there is an incorrect
substraction.
The existence of that risk is not really affected by a switch of
signedness. If the code incorrectly takes a detour through negative
values, but returns back to cor
On 10/8/24 9:25 AM, Gavin Smith wrote:
The question for me is not, "is C++ a good language". It is, "does
using C++ in Texinfo threaten the long-term future of the Texinfo project".
I can imagine a situation, hypothetically speaking, where a project gets
so large, so complicated, written using s
On Tue, Oct 08, 2024 at 05:05:59PM +0100, Gavin Smith wrote:
> On Tue, Oct 08, 2024 at 01:46:56AM +0200, Patrice Dumas wrote:
> > Hello,
> >
> > In the info reader, as part of an effort to avoid comparison of signed
> > and unsigned integers, and also to have a clearer code, I am considering
> > s
On Mon, Oct 07, 2024 at 09:24:34AM -0700, Per Bothner wrote:
>
>
> On 10/6/24 11:18 AM, Gavin Smith wrote:
> > Now imagine that half of DomTerm gets rewritten in Rust and then you
> > are scratching your head looking at a bunch of Rust code that you barely
> > understand when trying to fix proble
On Tue, Oct 08, 2024 at 01:46:56AM +0200, Patrice Dumas wrote:
> Hello,
>
> In the info reader, as part of an effort to avoid comparison of signed
> and unsigned integers, and also to have a clearer code, I am considering
> setting SEARCH_BINDING start and end offsets to size_t instead of long.
>
> Date: Tue, 8 Oct 2024 01:46:56 +0200
> From: Patrice Dumas
>
> Keeping long could hide some bugs of offsets becoming negative, but also
> be more robust in face of those bugs if it does not matter much that the
> offsets become negative.
>
> Any advice?
>
> I attach the patch that would set S
11 matches
Mail list logo
