amyc.parsing

package amyc.parsing

Members list

Type members

Classlikes

object Lexer extends Pipeline[List[File], Iterator[Token]], Lexers

Attributes

Supertypes
trait Lexers
trait Zippers
trait RegExps
class Pipeline[List[File], Iterator[Token]]
class Object
trait Matchable
class Any
Show all
Self type
Lexer.type
object Parser extends Pipeline[Iterator[Token], Program], Parsers

Attributes

Supertypes
trait Parsers
trait Debug
trait Operators
trait PrettyPrinting
trait Enumeration
trait Parsing
trait Syntaxes
class Pipeline[Iterator[Token], Program]
class Object
trait Matchable
class Any
Show all
Self type
Parser.type
sealed trait Token extends Positioned, Product

Attributes

Supertypes
trait Product
trait Equals
trait Positioned
class Object
trait Matchable
class Any
Show all
Known subtypes
sealed abstract class TokenKind(representation: String)

Attributes

Companion
object
Supertypes
class Object
trait Matchable
class Any
Known subtypes
object EOFKind.type
class KeywordKind
object LiteralKind.type
object ModifierKind.type
object NoKind.type
class OperatorKind
Show all
object TokenKind

Attributes

Companion
class
Supertypes
trait Sum
trait Mirror
class Object
trait Matchable
class Any
Self type
TokenKind.type
object TokenKinds

Attributes

Supertypes
class Object
trait Matchable
class Any
Self type
TokenKinds.type
object Tokens

Attributes

Supertypes
class Object
trait Matchable
class Any
Self type
Tokens.type
object keywords

Defines all the keywords of Amy To add a new keyword, only override Keyword

Defines all the keywords of Amy To add a new keyword, only override Keyword

case object <name> extends Keyword

Attributes

Supertypes
class Object
trait Matchable
class Any
Self type
keywords.type
object modifiers

Should we add them in parsing or in core or have 2 separate structures in both parsing and core ?

Should we add them in parsing or in core or have 2 separate structures in both parsing and core ?

Attributes

Supertypes
class Object
trait Matchable
class Any
Self type
modifiers.type