>From: "Hartmut Kaiser" <[EMAIL PROTECTED]> > Terje Slettebų wrote: > > > > typedef char (&yes_type)[1]; > > typedef char (&no_type)[2]; > > Within the Boost.Spirit library we have the need to have not only two > distinct (size-)types, but something around a dozen. Wouldn't it be > better to provide something more general as the two (size-)type yes/no > solution? With Boost.PP this shouldn't be any problem.
Sure, that would be fine. I'm not that familiar with Boost.PP, though, so I think I leave it to someone else to write that version. As quite a bit of code uses yes_type/no_type, now, it may be a good idea to keep them, as well, anyway, for backwards compatibility and simplicity. Regards, Terje _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
