Tickets :: Comment on [#158] Autogenerated SE types?

* Your Email Address
* Spam protection	Enter the letters below: _____ _____ _____ __ ____ __ / ____\|_ _\| __ \\| \/ \ \ / / \| (___ \| \| \| \|__) \| \ / \|\ \ /\ / / \___ \ \| \| \| ___/\| \|\/\| \| \ \/ \/ / ____) \|_\| \|_\| \| \| \| \| \| \ /\ / \|_____/\|_____\|_\| \|_\| \|_\| \/ \/
Comment	> Now we have enum of possible gloox's StanzaExtensions (enum > StanzaExtensionType), but it's boring and hard to use them, i.e. > "const VCardUpdate vcard_update = > presence.findExtension<VCardUpdate>(ExtVCardUpdate);" > I tell to method info about SE both by template and enum. But just > imagine how simpler become our source if we will give to method all > info just by template! > "const VCardUpdate vcard_update = > presence.findExtension<VCardUpdate>();" is easier, isn't it? > So, what are the ways for it?.. > I think, it's possible to create some macro, like this one: > #define REGISTER_STANZA_EXTENSION(SEClass) \ > template <> \ > int stanzaExensionType<SEClass>(SEClass t = 0) \ > { \ > static int type = -1; \ > if(type == -1) \ > type = registerStanzaExtension(#SEClass); \ > return type; \ > } > both with functions: > template <typename T> int stanzaExensionType(T t = 0) { return -1; } > GLOOX_API int registerStanzaExtension(const char *name); > second one should return positive unique integer value for different > name's and the same for equal ones. Invoking of method > stanzaExensionType<T>() is equal to guessing of correct enum. Also > macro should be used in this way: > REGISTER_STANZA_EXTENSION(gloox::VCardUpdate), namespace mustn't be skiped. > > What do you think about it?..
Attachment
Watch this ticket