I would just advise you against too much forward-thinking. Code for 'now', because you can't possibly predict the future.
When (or rather, if) you need feature X, you will also need Y. And you will have a concrete use case to reason against. Then you will come up with much better interface.
If you still persist, I'd rather make the Mesh class itself a container, like Cornstalks suggested.
dilyan_rusevMember Since 24 Nov 2006
Offline Last Active Yesterday, 04:43 PM
- Group Members
- Active Posts 148
- Profile Views 2,821
- Submitted Links 0
- Member Title Member
- Age 25 years old
- Birthday August 16, 1988
- Skype dilyan_rusev
dilyan_rusev hasn't added any contacts yet.