> | Note that the container mapping from menu position to the lyxfunc could be
> | as simple as a vector<string> for each container (I presume the integers
> | are the positions in the menu and therefore small).
>
> I foresee only one small problem, dynamically generated pseudo funcs.
> They need a name.
[Sounds easier to generate a string name than a unique integer id...]
> [...]
> well, i follow you completely when it comes to user interaction, but
> what if this is a script that builds a lyx document from, sya, xml
> sources over the lyxpipe? Then this overhead could be important.
Don't try to optimize unless you have had a look with the profiler.
I bet a box of beer that this won't happen. Poor argument, I know :-)
> Actually on std::map iterators are almost never invalidated. Almost
> only on deletion I think.
*sigh* You are right, I was wrong.
Andre'
--
André Pönitz ........................................ [EMAIL PROTECTED]
