Text design
From CSSEMediaWiki
(Difference between revisions)
Colin Fagg (Talk | contribs) |
m (Reverted edits by Ebybymic (Talk); changed back to last version by Lukas Korsika) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Design a class (or classes) to represent text, i.e. a sequence of characters. Support search and replace for subsequences. | Design a class (or classes) to represent text, i.e. a sequence of characters. Support search and replace for subsequences. | ||
| − | 1 proposed | + | 1 proposed design: |
[[Image:Proposal_1.png]] | [[Image:Proposal_1.png]] | ||
| + | |||
| + | Another proposed design would be to define an interface for Text, and first create a simple implementation that uses an array of characters to store the string, resizing it when necessary. If there are performance issues, we can create other solutions, for example a Text implementation that works like a treenode, by storing a left and a right Text, which it combines together. --[[User:Lukas Korsika|Lukas Korsika]] 01:13, 21 October 2010 (UTC) | ||
Latest revision as of 03:05, 25 November 2010
Design a class (or classes) to represent text, i.e. a sequence of characters. Support search and replace for subsequences.
1 proposed design:
Another proposed design would be to define an interface for Text, and first create a simple implementation that uses an array of characters to store the string, resizing it when necessary. If there are performance issues, we can create other solutions, for example a Text implementation that works like a treenode, by storing a left and a right Text, which it combines together. --Lukas Korsika 01:13, 21 October 2010 (UTC)
