| |||||||||||||
Glibc change exposing bugsGlibc change exposing bugsPosted Nov 10, 2010 22:49 UTC (Wed) by cesarb (subscriber, #6266)In reply to: Glibc change exposing bugs by mrshiny Parent article: Glibc change exposing bugs
> So punishing certain programs for license choice by making subtle (and sometimes unjustifiable) changes to API seems like a highly passive-aggressive approach to their ideology.
This was not an API change. The memcpy() API has always been that the regions cannot overlap, and has been so for decades. This was just a change in the implementation details.
(Log in to post comments)
Glibc change exposing bugs Posted Nov 11, 2010 0:33 UTC (Thu) by marcH (subscriber, #57642) [Link]
> This was not an API change.
Agreed, let's not confuse API change with "change of undefined behaviour". It may look the same but it is different.
|
|||||||||||||