Skip to content

Grease support for difference between platform's unicode support #183

@jbrichau

Description

@jbrichau

VAST has Unicode support using UnicodeString and Grapheme classes.
Pharo and GemStone have Unicode support built-in String.

Porting Seaside to VAST requires changes to the base code of Seaside instead of to platform-specific packages. Therefore moving this difference to Grease would be beneficial.

An example is WAJSONParser>>parseCharacterHex.

To be detailed further... this issue serves as the placeholder.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions