Re: what happened to that new isset() like language construct

Marcus Boerger wrote:

Hello Marc, it somply was far too lat3e in relase process. That's wy we ae all agreed to delay that until 5.1. Also we were very unsure about the name of such an operator....if you can collect all the ideas or can come up with ther perfect one!?!

Well I'm partial to ?: and there seemed to be some support for it, but there also seemed to be a non-trivial (though not necessarily difficult) amount of work to get it to work right. ifsetor() is obviously less concise, but also the name at first glance is a little non-obvious/confusing. I suppose isset() suffers from the same problem, and people will eventuall get used to it. If the technical problems can be overcome, I'm all for ?: otherwise ifsetor() seemed like the best suggestion so far. I am far less qualified to come up with an alternative than the more experienced PHP'ers out there. Marc