Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch
Newsgroups: comp.lang.c
Subject: Re: How to avoid an overflow during multiplication?
Date: Mon, 24 Jan 2022 11:28:35 -0800
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <86r18xlyqk.fsf@linuxsc.com>
References: <86v8ydp57h.fsf@linuxsc.com> <9_BGJ.170561$X2_b.72894@fx09.ams4> <86mtjopoq5.fsf@linuxsc.com> <86v8y9m8ba.fsf@linuxsc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="d742d26243a9575adb46fc0e29496190"; logging-data="13974"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18K5XfkQgGArpzQCjL65Swb8PkCnMoK3C8="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:+e+05VPZ9Nbkre8P+LydWA1JXp0= sha1:SLYH/8srONvANCeEAqeMkjchCrY=
Xref: csiph.com comp.lang.c:164591
scott@slp53.sl.home (Scott Lurndal) writes:
> scott@slp53.sl.home (Scott Lurndal) writes:
>
>> Tim Rentsch writes:
>>
>>> scott@slp53.sl.home (Scott Lurndal) writes:
>>>
>>> Surely you can find some example that wouldn't go against your
>>> existing agreements.
>
> Ok, a long C function: [...]
Good, thank you for tracking down what looks like a good
example.
Before I look any further, are there any particular aspects
you would say are important to pay attention to or that
contribute to difficulty in refactoring?