Olivier Berger wrote: > Le dimanche 05 septembre 2010 à 17:04 +0800, Thomas Goirand a écrit : >> Olivier Berger wrote: >>> Fine and perfectly good when it comes to do some testing on packages. >>> But I fear your requiring too strict reporting for production. After >>> all, it's just warnings about *future* deprecations [0] ! >> The warning is: >> >> PHP Deprecated: Assigning the return value of new by reference is >> deprecated in /usr/share/php/nusoap/nusoap.php on line 7381 >> >> It doesn't read "will soon be deprecated" but really *is* deprecated, >> which is the present tense. So it's deprecated *now* and will be >> completely unsupported in the future. >> > > Well... so we don't have the same interpretation of these PHP warning > message and docs. I think there's no more value in arguing more : we > won't change opinions it seems. > > Feel free to upload a fixed version if you're sure it's RC. > > Regards,
Hi Olivier, Thanks for your quick reply. There's no opinion here, or room for any interpretation. Are you seriously saying that "is" is the verb to be in the future? Or is it that you didn't you really understand the meaning of "not supported" as opposed to "deprecated"? As per: http://grammar.ccc.commnet.edu/grammar/to_be.htm "I am, we are, he/she/it is" is present tense. I can read: "Assigning the return value of new by reference *IS* deprecated" (not "will be" or "is going to be", or even "shall be"). Are you saying that I am giving an interpretation that deprecation is now, and not in the future? That this is only my view? Please consider it again, there's another proof of what I'm saying: http://php.net/manual/en/migration53.deprecated.php I can read: "Assigning the return value of new by reference is *now* deprecated." If you don't understand that "is" is the verb "to be" in the present tense, maybe seeing the word "now" in the above helps more? Note that I'm not trying to be aggressive, being bad to you or anything, but just trying to let you understand the meaning of the wording used here. I could respect your point of view if you were saying "I don't think a deprecation warning is an issue", but you are not. You are saying the opposite thing as what the warning says, and the opposite thing as what the PHP web site says about this issue. Deprecation is really happening *now*, for the PHP 5.3.x in Squeeze, and not in the future. It's the *support* of such deprecated function that will be removed in the future only, which is why it is deprecated now. Also, previously, on a private mail sent to me in French, you wrote that you agreed to fix by yourself, and I told you I would sponsor the upload of such a fix. Are you changing your mind here? There's something in your logic that I don't get. Please make a clear statement of your intentions and don't change it. Now, about uploading a fix, you told me that there's a security issue (an XSS vulnerability) being addressed currently by the security team, handled by Raphael. As a consequence, I can't upload such a fix before I hear back from the security team... Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
