Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Year and that's exactly my point and why it is stupid, because it uses
public interface whereas it can do things much more efficiently by
accessing directly to the data.
I agree it would be more efficient. But I am not sure it is worth
writing a new piece of code accessing the internals just for an
efficiency nobody cares about.
It is not "just for that". Writing this thing efficiently would be a
show case for other things: inserting strings, changing font properties
over a given range, replacing one string with another, etc. We might
even have some code sharing between those things at the end.
I am. "optimisation" is maybe not the good word but a good programmer
should always have efficiency in mind when programming, *always*.
Of course, but maintainability too. I prefer to have as little code as
possible to access the implementation details of ours structures.
Sure but this _is_ implementation in my mind. Only the character
container should know about the different character properties,
including case (even though this is not strictly speaking a property).
Abdel.
