2010/6/2 Ian Lance Taylor <i...@google.com>:
> As you say, gengtype includes specific support for VEC. Using
> std::vector instead will require some work in gengtype, but not too
> much. Currently gengtype generates code like this for a VEC:
>
> size_t l0 = (size_t)(((*x).base).num);
> for (i0 = 0; i0 != l0; i0++) {
> if ((*x).base.vec[i0].jump_functions != NULL) {
>
> It should be entirely feasible to make it generate std::vector
> accessor functions instead.
Ian, do you have an idea on how to avoid _M_impl dependency in
gengtype or what else to do about it?
Because we can trivially make gengtype mark the vector itself and mark
whatever was put into vector, but not _M_impl.
--
Laurynas
