Re: Re: [PEPr] Comment on RFC::EvalForbiddance

On Tue, 16 Aug 2005 08:39:38 -0700 clay@killersoft.com (Clay Loveless) wrote: > Pierre-Alain Joye (pierre@dotgeek.org) wrote: > > > This is the perfect example of a bad usage of eval. Not having > > serious security issue (if $obj is defined and used only in > > this scope), but still horrible. And eval raises notices too... > > > > A tip, class_exists('myclass') && $obj instanceof myclass, > > but this is not the topic, that fits more in php-general. > > Pierre, > > Apparently you haven't done any coding that attempts to avoid > "is_a" deprecation warnings in PHP5 and the parse errors that > "instanceof" usage causes in PHP4. Again, you have no clue about what you are talking about. The patch was rejected and there is maybe a little chance to get is_a undeprecated in next RC. > There's been some discussion of this usage of eval() over the > past couple of months [1], and I don't recall you telling any of > those people that "their safe" was on php-general [2]. And? You like to have paid support or? > Please don't make our disagreements of late personal, Pierre. And > even if you must make them personal, a personal attack on me is > still no excuse for spreading FUD about eval() usage in regard to > PHP4/PHP5 code compatibility. It's not a personnal attack, it's only an attempt to make you realize how most of comments are senseless. Besides that I do not care that much about what one can think about me or not. --Pierre