reportsvn_loginterpretparserpcgslprinterscannerastArithmeticOps-IntBooleanOps-CardEntsBooleanOps-CardsBooleanOps-IntBooleanOps-StringControlFlow-ifControlFlow-Start-Play-WinningControlFlow-WhileFunctionsGetTypeGlobalAssignmentAccesshighcard.cgsIO-input-outputListAppendListAssignmentAccessListLengthMakefilepoker.cgsprintdeckRandstdlib.cgltest-basic1transfertransfer-randVarAssignmentAccessPCGSL: Playing Card Game Simulation LanguageEnrique [email protected] [email protected] [email protected] [email protected] W4115Programming Languages and TranslatorsDecember 19, 2008Contents1 Introduction 31.1 Simple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Language Tutorial 43 Language Manual 53.1 Lexical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.1.1 Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.1.2 Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.1.3 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1.4 Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1.5 Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1.6 Meaning of Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1.7 Scope, Namespace, and Storage Duration . . . . . . . . . . . . . . . . 73.2 Declarations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2.1 Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2.2 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.2.3 Special Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.3 Expressions and Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.3.1 Precedence and Association Rules in PCGSL . . . . . . . . . . . . . . 93.3.2 Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.3.3 Function Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.3.4 Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.4 Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.4.1 Expression Statements . . . . . . . . . . . . . . . . . . . . . . . . . . 1213.4.2 Selection Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.4.3 Iteration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.4.4 Jump Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Project Plan 144.1 Planning & Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.2 Development & Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.3 Programming Style Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.4 Project timeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.5 Roles and Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.6 Software Development Environment . . . . . . . . . . . . . . . . . . . . . . . 184.7 Project Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Architectural Design 192Chapter 1IntroductionThe Playing Card Game Simulation Language (PCGSL) is designed to be a simple program-ming language for programming card games. Our language allows a programmer to workwithin a standard set of conventions and procedures for playing card games, without havingto write a large amount of code as one would have to in a general-purpose language. Thisallows the programmer to focus on creating randomized simulations of popular games orhands, as well as quick mock-ups of new games based around standard 52-card decks.1.1 SimplePCGSL is simple to learn. Using well known C-style imperative syntax conventions, ourlanguage...3Chapter 2Language Tutorial4Chapter 3Language Manual3.1 Lexical ConventionsThis section covers the lexical conventions including comments and tokens. A token is aseries of contiguous characters that the compiler treats as a unit. Blanks, tabs, newlines,and comments are collectively known as white space. White space is ignored except as itserves to separate tokens. Some white space is required to separate otherwise adjacentidentifiers, keywords, and constants. If the input stream has been parsed into tokens up toa given character, the next token is taken to include the …
View Full Document
Unlocking...