Well, in the past, I've had information about an author and his stories stored in three variables, $authinfo, $sc, and $sinf. Thus, each array doesn't actually contain contain a story and it's corresponding values (you'd think that would be the most logical way to do it).
I had been toying with the idea of porting all the data to something like $storyarray['storyname']['storyattribute'] but I learned about objects! They sounded really cool, and I thought that when I was creating a story array, I had to make a call to the database and get the appropriate elements and stuff. __initialize would work perfect for this! Plus, by blueprinting a class, I would be able to explicitely say what variables were allowed, and which ones were not, while having the extendability (for like, Chapter information) that Arrays offer. It would help solve a lot of my "Undefined Index" woes.
But "Try it" that's a very good idea. I should have thought of that,

.
Code: Select all
$authorarray[$authorobject->current]->{$storyobject->current}->title;
//I hope grouping is supported... time to start testing!
Hmm... now we just have to figure out serialize(). Serialize is fast, right?
EDIT: After seeing Feyd's second post, my question is they are to be defined seperately, but should they be defined within the author class if they're only going to be used there? And Class definitions are global, correct?