On Fri, 2009-09-18 at 10:35 +0100, Gavin Wraith wrote: > In message <[email protected]> > you wrote: > > > > It would be good if we could design a solution that avoids the need for > > > these duplicate CSS contents, > > This comment may be entirely impracticable, because it comes from somebody > out of the loop - and from a considerable distance from the action. > Surely, with a project that involves memory management, string internment > and separate contexts, the answer is to use something like the Lua core > library that manages all these things, with scripting as an added bonus, > as a bottom layer. Or are there other factors that preclude it?
Well, we already have the ability to intern strings -- test builds have been using it for some time. So, internment itself is not the issue here. The problem that exists, as I described, is that the way we currently manage internment contexts that it's less useful that it could be. I'd like to make it more useful, but am currently out of good ideas for how :) J.
