Re: optimising OUString for space

On Mon, 2012-10-01 at 14:23 +0200, Noel Grandin wrote:
> Perhaps we need to split out some preparatory tasks?
> For example
>   - fix code that directly accesses the underlying buffer

        Sure !

>   - create an external iterator class (which would currently be a thin 
> wrapper around int) for looping over the buffer and indexing into it
> -  fix code that indexes into an OUString to use the new external iterator

        That is all well worth doing of course; I imagine that improving
instances of our splitting / tokenising code left and right would also
be rather useful having some nice, standard, C++ iterators there that
avoided people having to use indexes left & right would yield a nice big
cleanup I think :-)

> Once those tasks are taken care of, the actual conversion to using UTF-8 
> internally will become a great deal simpler.

        Indeed; it would make a good start. Then again - in terms of useful
re-factoring, Caolans' nice UI / layout stuff looks like it has tons of
potential to create real user-visible improvement :-)

        ATB,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot