Developer forums (C::B DEVELOPMENT STRICTLY!) > Compiler Framework Redesign

cbVariant class - update: discarded

<< < (3/4) > >>

rickg22:
Hmmm....

Interesting. Anyway I think i made up my mind, we'll use a very basic version (mine :P ) of variant. For storing the configs we shouldn't use advanced types other than wxString. Arrays should be handled with cbProperty classes.

takeshimiya:
Good enough for the purpose I think.
If you have any design concerns look at the boost.any.

killerbot:
to quote Thomas ... ***shudders***
Storing a type in the class and using unions.
Last month in Vegas several Gurus were flaming against those kind of things.
I'd say templates (I don't consider them a burden), leave the work up to the compiler.

Just another 'little' remark, when talking about the new features, maybe it's better to not think about implementation details yet (like using a tree) ??

Anyway, time to think and think ... ;-)

Lieven

thomas:

--- Quote from: killerbot on December 30, 2005, 09:41:45 am ---to quote Thomas ...
--- End quote ---
Hey, don't use my name in the same thread as the word variant... I am not involved in this :P
But yes, you are right, Lieven.

TDragon:
Personall, I'm not clear on what exactly your map/tree of variants does in the compiler framework. The only things I can envision requiring something like that would be handled more gracefully by inheritance and polymorphism. (But then, I've never sat down and designed a compiler framework before, so I'm probably missing something.)

Navigation

[0] Message Index

[#] Next page

[*] Previous page