in reply to Re: Flat File Fun (or You Just Saved My Class)
in thread Flat File Fun (or You Just Saved My Class)

Okay, so here's how the data breaks down:

The idea is the project will be a rideshare program. The idea being that each one of these objects shown will be shown to the user as a unique ID (so that they can do specific actvities.) Each portion of the data structure is built by the user and it needs to persist between runs so that it can continue to be modified. For the scope of this project, I don't need to worry about more than 1 user accessing the program at a time.

One posibility is to just add the unique IDs that I'm giving to the user to the actual objects and ignore inheritance all together; however, doing that would make the implimentation of this system much more difficult. It is true that certian "modes" of this program will not require the whole structure to be rebuilt; however, these repesent the minority of all cases.
==
Kwyjibo. A big, dumb, balding North American ape. With no chin.
  • Comment on Re: Re: Flat File Fun (or You Just Saved My Class)

Replies are listed 'Best First'.
Re: Flat File Fun (or You Just Saved My Class)
by Abigail-II (Bishop) on Jul 16, 2003 at 15:24 UTC
    Given my previous post, you aren't thinking that I now tell you what to do, just based on two small paragraphs of description, one of which is just exploring a possibility?

    Make an implementation, then we'll see.

    Abigail

[reply]
      On the other hand he can make the implentation with the stor meathod in mind. Depending on how he implements, his store becomes more or less complicated. What is wrong with him getting options before he implements?

      -Waswas
[reply]
        He wasn't asking what his options were. He was asking what the best method would be. Quite a different question, and certainly not answerable at this point of the design.

        Abigail

[reply]

In Section Seekers of Perl Wisdom