Le mercredi 04 mai 2011 14:23:19, Aurelien Jarno a écrit : > Le 04/05/2011 14:06, Raphael Hertzog a écrit : > > a nice behaviour, it would be way better to print > > a warning and fallback to a correct behaviour. Users can then report the > > problems without experiencing a non working-application. > > Printing a warning on a thing that is potentially used everywhere, > especially in scripts is not a good idea. It will simply corrupt the > data that the othe part of the script is waiting for, and that even on > stderr, a lot of scripts are not (correctly?) designed for that. Is there a usertag to track the memcpy bugs? Regards.
Description: This is a digitally signed message part.