Status: Workneeded
Owner:
[hidden email]
Labels: Type-Cleanup Milestone-2.0
New issue 6219 by
[hidden email]: LeadingChar in Strings removal
http://code.google.com/p/pharo/issues/detail?id=6219It is time, and I need an issue number for the slices made as it progresses.
(Can be found in PharoTaskForces)
This is an extensive change that will involve and hopefully simplify
Scanners, Fonts, Strings, Environments, Charsets, Converters, and
potentially more.
The main rationale is that we want all Characters/Strings/Symbols used
internally in Pharo to unequivocally answer codePoints from the Unicode
character set when asked value/at:
Some details of the intended end result:
- It will allow for saving space by implementing String-subclasses using
different codePoints interally, at the cost of performance, though none
will be provided by default. (Currently, both space and performance suffers)
- leadingChar will be turned purely into an implementation detail of
Composed Text encoding, as it should be.
- There will be no link the the current locale/environment, and most
likely, Environments will be deemed unnecessary and removed.
- StrikeFontSets will no longer delegate display to a specific font with
glyph coverage based on a leadingChar of a character, but on its unicode
codePoint
- CharacterScanners will not differentiate on the class of the string which
method to use to scan, but delegate to the string itself which method
should be used to scan it.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Locked
