> Why don't we get rid of the string-based encoding, at least when the > functionality is invoked from the GUI ? > > I mean, something where we put into the LFun a direct pointer to this new > struct you're talking about, then > we use that in lyxfind.cpp instead of encoding/decoding strings. > > If the user invokes it via the mini-buffer (or the Python extensions or > whatever else), then we'll have a parsing > of the strings into that struct, and still dispatch a "binary" LFun. >
It makes sense I guess. Would it be this simple for all LFUNs ? Are there other catches to it ? > T. Vincent
