On Mon, Dec 29, 2008 at 1:21 AM, Gwern Branwen <[email protected]> wrote:
> I see. So looking at it, seemed best to define a Unicodable String > type and pattern-match from there. This breaks the (potential) syntax-level analyzers. The problem is that Unicodable blends together many categories of tokens. Reserved operators should be reserved operators, etc. You can add a string argument to Operator and Identifier if you wish. [[ and ]] should definitely not be matched as one Unicodable, each bracket is a separate symbol! btw I think we should leave user-defined operators/identifiers alone. As I understand it one can create one's own unicode operators, therefore this can be extremely confusing. Users that want that can always put it in their own config. Cheers, JP. --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
