Let me make an attempt to clarify what I originally requested.
------
A function/construct named setor() modeled after isset(), which takes 2 parameters:
parameter 1, the variable in question parameter 2, the default value
if(isset($parameter1))
return $parameter1;
else
return $parameter2;The following requirements would apply:
1. The function would not throw a notice if $parameter1 was not set 2. The second argument would not be evaluated unless it was actually needed 3. The first argument would not be modified in any way. ------
After a lengthily discussion today on the internals list, I have come to the conclusion that this is not possible to adhere to all three of the above requirements in user-land, but would be simple to do in internal-land.
We have more-or-less concluded that an operator would not be the way to go. We have also seen a general consensus that this would be a highly helpful feature for developing in E_ALL error mode.
I'm not quite sure how the decision making process goes on in this project, is it Andi that has the final say?
I would like to see a general consensus on:
1. Is it a feasible feature that would not interfere with the overall goals of PHP?
2. If so, can we schedule it to be implemented in a upcoming version of PHP?
2. If not, can I pay an experienced developer to take the time to implement it into an upcoming version of PHP?
I'm not trying to get in the way of the PHP development process, frankly, I'm new to this side of things. But I do have quite a few personnel on payroll that I think would benefit significantly by having a this feature added, which is why I would be willing to pay for it's implementation, which in turn everyone can benefit from.
Thanks again,
Jason Garber President IonZoft, Inc.
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
