Sujet : Re: "undefined behavior"?
De : janis_papanagnou+ng (at) *nospam* hotmail.com (Janis Papanagnou)
Groupes : comp.lang.cDate : 15. Jun 2024, 06:03:16
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v4j7ak$3aorq$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
On 15.06.2024 06:45, DFS wrote:
On 6/14/2024 11:56 PM, Keith Thompson wrote:
DFS <nospam@dfs.com> writes:
>
After casting i to an int before any array addressing, // works.
>
I'm surprised you needed to convert i to an int. I would think that
just replacing nums[i/2] by nums[i//2] would do the trick,
as long as i always has an int value (note Python's dynamic typing).
If i is acquiring a float value, that's probably a bug, given the name.
I spotted the issue. Just prior to using i for array addressing I said:
i = N/2.
The fix is set i = int(N/2)
Given what Keith suggested, and assuming N is an integer, wouldn't it
be more sensible to use the int division operator '//' and just write
i = N // 2 ? I mean, why do a float division on integer operands and
then again coerce the result to int again?
Janis
"undefined behavior"?
Re: "undefined behavior"?