44
« on: June 12, 2008, 06:02:05 am »
tchristney
We could use the base struct for installations and it was the first thing i considered.
The reason i considered a separate struct was that there is alot of information in the base struct that isn't needed for an installation.
But i think there is two questions here that need to be answered:
1) Can installations just be normal bases, so you could just build bases for specific purposes
My understanding was that the answer to this question is no. We want to keep a base limit?
Also the ufo yards need to be handled outside of the base.
2) Should we use the existing base struct or create a new struct and code to handle installations?
I'm happy to go either way on this one. we can just define a new "base_t installations" in global data.
My only issue is that it then could become confusing and a little unwieldy as its not just one or two fields not being used but quite a lot. And a simpler struct may be more effective.
Obviously my struct is just a cutdown version of the base_s struct with a few additions.
Steve