[m-rev.] lex and moose changed

[Michael Day]

> A sequence or stream type class should solve that.  I'd define a sequence as
> having an emtpy/1 predicate and a next/3 predicate that returns the next and
> rest.  A stream would be the same as a sequence, except it would have only
> unique (destructive) modes.

You've just hit a snag there: the token predicates I was using depended on
being able to backtrack to find the longest matching token. A stream type
class with unique modes would be the same as using read_char now. It would
be nice to have a stream that used transparent putback on backtracking.

Michael

--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------