markw@mohawksoft.com wrote:
>> markw@mohawksoft.com wrote:
>>> [snip]
seems the perceived problem is being caused by something else?
>>> Sorry, I have to respectfully disagree.
>> ok :-).
>
> Men of integrity must be able to disgree peacefully. :-)
>
:-)
>
> Well, the point I was try
> markw@mohawksoft.com wrote:
>> [snip]
>>> seems the perceived problem is being caused by something else?
>>>
>>
>> Sorry, I have to respectfully disagree.
>
> ok :-).
Men of integrity must be able to disgree peacefully. :-)
>
>>
>> I was converting all indexes to string indexes, and simply usin
markw@mohawksoft.com wrote:
> [snip]
>> seems the perceived problem is being caused by something else?
>>
>
> Sorry, I have to respectfully disagree.
ok :-).
>
> I was converting all indexes to string indexes, and simply using
> "zend_hash_update" to re-constitute the objects and they simply di
Mark wrote:
> Mark wrote:
>
>> I have an extension that seems to create PHP variables correctly, and
>> var_dump() doesn't seem to have a problem. but upon moving to 5.1.x it
>> fails.
>>
>> Anyone have a suggestion?
>
> Well, it is fixed. Evidently, PHP 5.1 sees a difference between $var["0"]
>
[snip]
>
> seems the perceived problem is being caused by something else?
>
Sorry, I have to respectfully disagree.
I was converting all indexes to string indexes, and simply using
"zend_hash_update" to re-constitute the objects and they simply did not
work. When I scanned indexes strings to test
Mark wrote:
> I have an extension that seems to create PHP variables correctly, and
> var_dump() doesn't seem to have a problem. but upon moving to 5.1.x it
> fails.
>
> Anyone have a suggestion?
Well, it is fixed. Evidently, PHP 5.1 sees a difference between $var["0"]
and $var[0]. It never did
6 matches
Mail list logo
