[Tickets #5604] Re: ListMessages endless loop

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5604
-----------------------------------------------------------------------
 Ticket             | 5604
 Updated By         | Michael Slusarz <slusarz at horde.org>
 Summary            | ListMessages endless loop
 Queue              | DIMP
 Version            | 1.0-ALPHA
 Type               | Bug
-State              | Feedback
+State              | Resolved
 Priority           | 1. Low
-Owners             | 
+Owners             | Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2007-08-07 22:36) wrote:

You live, you learn.  Turns out you can't have numeric properties in an
object - or more accurately, your property can't begin with an integer
(i.e. you can't have $obj->1 or $obj->1foo).  And it turns out that
encoding $msglist as a regular array does return the correct
"{'integer':integer,'integer2':integer2}" form.  I know for a fact this did
not work like this before - but I think the difference now is that we build
$msglist ourselves now earlier in the function - and since we are creating
the array directly by doing $msglist[integer] calls, PHP is interpreting
these indices as string indices.  I can almost guarantee you before we were
building via $msglist[], or maybe an array_keys() or array_values() call,
or something similar that resulting in the array being created with indexed
integers rather than string indices.