Search:

Type: Posts; User: aussiemcgr

Search: Search took 0.21 seconds.

  1. Re: How to Logically Break Down a System for Inheritance

    It shouldn't violate that. When you load the data in, you have to load it into somewhere. What I was suggesting was a single central data core which can be used to lookup values.
    Perhaps it would...
  2. Re: How to Logically Break Down a System for Inheritance

    Ok, I'm going to suggest a bit of a different take on this. We are going to use some creative data storage and referencing to reduce your need to do lookups and whatnot.
    Tell me if these guidelines...
  3. Re: How to Logically Break Down a System for Inheritance

    You could do something like that, but there are probably better options.
    When designing a data structure, you need to ask: how am I going to access the data?
    Should the data ALWAYS be sorted a...
  4. Re: How to Logically Break Down a System for Inheritance

    You could create multiple layers of inheritance. Something like this:
    Location (abstract or interface) - contains: name, area
    POI (concrete, extends/implements Location) - contains any new stuff...
Results 1 to 4 of 4