Yeah, this is something I got confused about too, until Chris set me straight. Duh - I wrote it - and then I got confused about it. I can be dumb as a box of rocks sometimes. The linked list or array or vector or whatever holds pointers to struct htmlTag, not the struct itself. So structs can go ahead and point to each other as parents and children, because the structs don't move. The growing vector simply reallocates the list of pointers to those structures.
I already do this, don't I? t->controller is the form that owns the input tag, and for an option t->controller is the select that owns the option. Just rename controller parent and you're halfway there. So with this in mind static list < struct htmlTag *>htmlStack; becomes static vector < struct htmlTag *>htmlStack; Then sure it's all normal after that, and I'd just love to set cw->tags to htmlStack, but cw->tags is one of those things that is in C, not C++. In fact it's in eb.h, thus in every C file, so we'd have to use void * or some such, or convert the whole project to C++. But that's the idea, and we can certainly move forward there. Then there is no trouble adding new tags as we need to, as js creates new thingees for us. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
