2009/8/26 Ralph Deffke <ralph_def...@yahoo.de>:
> sorry I mixed 'set' with 'given' and if my mistake did prevent all the
> smarter guys to give u an answer I'm sorry too.
> I hope not to be too limited to give u an answer
> well, think about how PHP >5 works.
> $a e.g. is a REFENCE to some memory where the variable resides.
> so the interpreter running into this unset() statement searches the
> reference table to find the pointer named $a to delete its name from the
> reference table. it doesn't find it, but it's ment to unset it anyway, why
> should be complained about it. in the next line the $a is not set, as u want
> mmmh nice as well that nobody told me direcly that I mixed set with given
Excuse me? I told you as soon as I knew that's why you were getting it so wrong.
> ps.: great behavior, I think for less then 10% of the world population is
> english the native language, such a behavior prevents very good and smart
> programmers arround the world to share their knowledge.
I actually think it's perfectly reasonable to expect people
contributing to this mailing list to have a good grasp of the English
language... at least enough not to make errors like the one you have
here. I understand how rude it can appear but I think it's important
that information resources such as this are as reliable as possible,
and if that means you need to be a bit more careful about asserting
your expertise when there's a chance that you've misunderstood the
question. I see no difference between misunderstanding due to language
issues and misunderstanding due to having not read the question
correctly. They both have the same effect.
Maybe I'm being too harsh. I'm sure you have a lot of knowledge to
share, but if you want to participate in what is an English mailing
list please be more careful in future.
Now, on to my real problem with the way you answered the question.
After your initial mistake you proceeded to, as far as I can tell,
completely fabricate a reason for the behaviour you were seeing with
absolutely nothing to back it up whatsoever. And then, despite being
corrected you repeated it. That's what I really objected to - anyone
can misunderstand a question, but filling in the blanks from thin air
helps nobody. Ever.
And that's all I've got to say about that. Now, about that holiday...
> "Tom Worster" <f...@thefsb.org> wrote in message
>> On 8/25/09 5:00 AM, "Ralph Deffke" <ralph_def...@yahoo.de> wrote:
>> > of course its a syntax error, because unset() IS NOT A FUNCTION its a
>> > language construct
>> that's hard to believe. i can't imagine how the compiler could reliably
>> predict if the argument will be set or not when the unset line is
>> > "Stuart" <stut...@gmail.com> wrote in message
>> > news:a5f019de0908250201g14e4b61cn73c6cd67da6f...@mail.gmail.com...
>> >> 2009/8/25 Ralph Deffke <ralph_def...@yahoo.de>:
>> >>> causes an error
>> >>> Parse error: parse error, expecting `T_STRING' or `T_VARIABLE' or
>> > in
>> >>> C:\wamp\www\TinyCreator\testCrapp6.php on line 42
>> >> This is a syntax error, not a runtime error. You've clearly done
>> >> something wrong.
>> >>> "Tom Worster" <f...@thefsb.org> wrote in message
>> >>> news:c6b87877.11463%...@thefsb.org...
>> >>>> is it the case that unset() does not trigger an error or throw an
>> >>> exception
>> >>>> if it's argument was never set?
>> >> Absolutely.
>> >> -Stuart
>> >> --
>> >> http://stut.net/
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php