日本欧洲视频一区_国模极品一区二区三区_国产熟女一区二区三区五月婷_亚洲AV成人精品日韩一区18p

SCC312代做、代寫Java編程語言

時間:2024-03-08  來源:  作者: 我要糾錯



February 2024 1 SCC312 Compilers Coursework 23/24
SCC312 Compilers Coursework 2023/24:
Recursive Descent Recogniser
1. General Instructions
Section 3 describes a grammar for a simple programming language rather like Ada. The task is to implement a
syntax analyser (SA) for this language using a recursive descent parser. The analyser’s sole function is make sure a
user’s source program is syntactically correct, and the SA should generate appropriate and helpful error messages
where required. The SA should terminate on encountering and reporting the first error. To be more precise, you
are expected to build a Syntax Recogniser with its purpose to recognise its input as a valid sentence in the
language specified by the grammar.
The coursework task is to implement part of a compiler for this language using a recursive descent parser.
1.1. Java Classes Provided
You are provided with the following Java classes:
(a) Token in a file Token.java, to represent a token returned by the lexical analyser stage. This has:
• a set of integer constants (becomesSymbol, beginSymbol, identifier, leftParenthesis, and so on)
representing the possible types of token in this language
• three public attributes (symbol, an int, which is one of the constants declared above; text, a String,
the characters making up the token; lineNumber, an int, the number of the line containing the
token)
• two constructors, and a static method getName to return the name (a String) of a token provided
as the single int argument
(b) CompilationException in a file CompilationException.java (see below)
(c) LexicalAnalyser in a file LexicalAnalyser.java, which is the lexical analyser for this programming language.
This has:
• a constructor with one String argument, the name of the file from which the tokens are to be read
• a method getNextToken (with no arguments), to return the next token read from the source text
• a main method, with which the operation of the lexical analyser can be tried out on a suitable file
(using a toString method supplied in the Token class)
(d) AbstractGenerate in a file AbstractGenerate.java. This is the abstract class you need to make concrete in
the Generate class you have to provide.
(e) AbstractSyntaxAnalyser in a file AbstractSyntaxAnalyser.java. This is the abstract class you need to make
concrete in the SyntaxAnalyser class you have to provide.
(f) Compile in a file Compile.java. This is the driver program for the whole coursework. This driver program
calls the parse method of the SyntaxAnalyser class for each file with a name of the form "programn"
(integer n ³ 0) (these files are in the coursework pack).
These classes can be found in the coursework pack ZIP folder that this document came along with. To help you
build and run your work, as well as generate this ZIP file to submit, some shell scripts have been included:
February 2024 2 SCC312 Compilers Coursework 23/24
1.2 Building the Code
For Windows Users:
Running ‘compile.bat’ will compile all java source files
Running ‘execute.bat’ will run the compiler against all supplied test programs
For Mac/Linux Users:
A makefile has been included which has the following functions (where ‘$>’ is your terminal prompt:
$> make
Compile all required java sources
$> make run
Run the compiler against all supplied test programs
$> make package
Build a submission .zip file - this is a ‘beta’ feature, check your submission file
has been created successfully before actually submitting it!
Note; The makefile requires a working install of the following: zip, java, javac, and make to work
correctly.
1.3 Java Classes To Be Implemented
1.3.1 SyntaxAnalyser
Write a Java class SyntaxAnalyser. Your SyntaxAnalyser class must include at an appropriate place a comment
line which includes the string "author" and your name.
The AbstractSyntaxAnalyser class contains the following methods :
abstract void _statementPart_()
throws IOException, CompilationException
abstract void acceptTerminal(int symbol)
throws IOException, CompilationException
public void parse(PrintStream ps)
throws IOException
You have to extend the above class as appropriate. Please note that the parse method is provided for you.
1.3.2. Generate
The parser must make use of the Generate class, which you must also supply by extending the AbstractGenerate
class. The AbstractGenerate class contains the following methods:
public void insertTerminal(Token token);
public void commenceNonterminal(String nonTerminalName);
public void finishNonterminal(String nonTerminalName);
public void reportSuccess();
public abstract void reportError(Token token, String explanatoryMessage)
throws CompilationException;
February 2024 3 SCC312 Compilers Coursework 23/24
The parser must demonstrate its operation by calling the Generate class methods as follows:
● insertTerminal(Token token) when it has correctly read a terminal.
● commenceNonterminal(String nonTerminalName) and finishNonterminal(String nonTerminalName) when it
respectively starts and finishes reading a non-terminal. For non-terminals specified in the grammar below, the
String nonTerminalName should be that specified in the grammar (for example "<procedure list>" or
"<assignment statement>"). For new non-terminals introduced by you, the String nonTerminalName should be
of the form "<new SOMETHING>".
● the void method reportSuccess() when it has successfully parsed the file.
Use these methods in a class Generate to display a trace (using System.out.println) of the operation of the
parser.
Error recovery is not required for this parser. Instead parse should report at the first syntax error encountered,
by calling reportError(Token tokenRead, String explanatoryMessage) in the Generate class. Implement a
suitable version of this method to indicate what the next erroneous token is, what the parser is trying to
recognise at this point, and the line number where the error is recognised. The method should finish by throwing
the exception CompilationException, which should eventually be caught by the parse method in the
SyntaxAnalyser class. As the exception reaches each of your parse methods, you should use it as an opportunity
to report where in the parse tree the error occurred. Hint: Look at the constructor for CompilationException.
The parse method should return in the normal way after processing a file, whether it reports success or failure, so
that it can then be called to start to process the next file (if any).
You may include in your Generate class either or both the constructor methods Generate() and Generate(String),
but no other methods than those specified in AbstractGenerate.
You should strive to make your error messages as helpful and as accurate as possible. You should consider how
the structure of the program can be used to get context for errors. We are deliberately not providing sample
error messages res.txt file but you should consider what a programmer of the language would need. When using
if statements, if you have more than 2 branches, please use a switch statement instead.
1.4 Marking criteria
Marks will be allocated according to the following criteria. The percentages are provided to guide you as to where
to dedicate your time and should be considered indicative only.
- SyntaxAnalyser (structure, design and implementation) 50%
- Generate (methods used, implemented and extension) 10%
- For the programs in the test set: 10%
- Success on syntactically correct programs: -
- Errors on syntactically incorrect programs:
- Detailed (correct) error messages 10%
- Recursive errors (stack traces) 10%
- Code quality and comments 10%
The coursework will be checked using a two step process; first automatically using a testing framework against
our provided classes and then manually to review the quality of your error messages, code commenting and other
criteria, and then finally marked according to letter grades.
February 2024 4 SCC312 Compilers Coursework 23/24
1.5 Test Data
The source texts to be analysed can be found in the “Programs Folder” provided. The output from “program0” is
provided as a guide as to what is expected in the way of output, so there is no need to include the results of
recognizing “program0”. To make it easier to see where sections start and end, I have indented the output for
program0, but note that you are not required to do the same in your output. Note: we will not be answering
questions about which programs should throw errors or fail to compile. Feel free to create your own sample
testing programs to test partial solutions while you are developing things.
2. Submission of Work
You should submit:
Listings of the code you have written (the classes SyntaxAnalyser and Generate, suitably laid out and
commented), and all the output from running your code over test files, both output.txt and res.txt should be
submitted. If you are using Mac or Linux, the makefile will help you do this.
Please note we have provided sample output from our worked solution on “program0”; you should use this as a
guideline for the output your recogniser produces, and as a check for the results of your recogniser on
“program0”.
Deadline: 16:00 (4pm), Friday, Week 19
WARNING : You *must not* change any of the pre-supplied Java classes. The 2 classes you submit will be
compiled and tested with the pre-supplied classes. If they fail to compile or run because they depend on some
alteration you have made to the pre-supplied classes, you will receive a mark of zero. Please ensure that you test
on the SCC lab machines with the version of Java installed there.
3. Grammar Rules for part of a Simple Programming Language
<statement part> ::= begin <statement list> end
<statement list> ::= <statement> |
<statement list> ; <statement>
<statement> ::= <assignment statement> |
<if statement> |
<while statement> |
<procedure statement> |
<until statement> |
<for statement>
<assignment statement> ::= identifier := <expression> |
identifier := stringConstant
<if statement> ::= if <condition> then <statement list> end if |
if <condition> then <statement list> else <statement list> end if
<while statement> ::= while <condition> loop <statement list> end loop
<procedure statement> ::= call identifier ( <argument list> )
<until statement> ::= do <statement list> until <condition>
February 2024 5 SCC312 Compilers Coursework 23/24
<for statement> ::= for ( <assignment statement> ; <condition> ; <assignment
statement> ) do <statement list> end loop
<argument list> ::= identifier |
 <argument list> , identifier
<condition> ::= identifier <conditional operator> identifier |
identifier <conditional operator> numberConstant |
identifier <conditional operator> stringConstant
<conditional operator> ::= > | >= | = | /= | < | <=
<expression> ::= <term> |
<expression> + <term> |
<expression> - <term>
<term> ::= <factor> | <term> * <factor> | <term> / <factor>
<factor> ::= identifier | numberConstant | ( <expression> )
An "identifier" is a sequence of one or more letters (a to z, A to Z) and digits (0 to 9), starting with a letter, and
excluding all the reserved words shown in bold above (procedure, is, integer, etc). Have a look at the
initialiseScanner method in LexicalAnalyser.java.
A "numberConstant" is a sequence of one or more digits (in which case it is of type "integer"), perhaps followed
by a decimal point and one or more digits (in which case it is of type "float"). A "stringConstant" is a sequence of
one or more printable characters (except ") with a " character at each end. Comments start with the symbol --
and terminate at the end of the line.
The distinguished symbol is <statement part>.
This simple language has no boolean or character data types; no arrays or records; no functions; the actual
parameters of all procedures must be identifiers, and are called by reference; only simple boolean expressions
(no not, and or or); only simple numerical expressions (no unary minus).
The grammar as written is not LL(1); it has left-recursive rules of the form:
<X list> ::= <X> | <X list> separator <X>
and rules of the form:
<something> ::= a X b | a Y g
where a, b and g are strings of terminals and/or non-terminals (a non-null) and X and Y are different
請加QQ:99515681  郵箱:99515681@qq.com   WX:codehelp 

 

標簽:

掃一掃在手機打開當前頁
  • 上一篇:代寫DTS304TC、代做Java/c++程序語言
  • 下一篇:代做COMP27112、代寫Java語言程序
  • 無相關信息
    昆明生活資訊

    昆明圖文信息
    蝴蝶泉(4A)-大理旅游
    蝴蝶泉(4A)-大理旅游
    油炸竹蟲
    油炸竹蟲
    酸筍煮魚(雞)
    酸筍煮魚(雞)
    竹筒飯
    竹筒飯
    香茅草烤魚
    香茅草烤魚
    檸檬烤魚
    檸檬烤魚
    昆明西山國家級風景名勝區
    昆明西山國家級風景名勝區
    昆明旅游索道攻略
    昆明旅游索道攻略
  • NBA直播 短信驗證碼平臺 幣安官網下載 歐冠直播 WPS下載

    關于我們 | 打賞支持 | 廣告服務 | 聯系我們 | 網站地圖 | 免責聲明 | 幫助中心 | 友情鏈接 |

    Copyright © 2025 kmw.cc Inc. All Rights Reserved. 昆明網 版權所有
    ICP備06013414號-3 公安備 42010502001045

    日本欧洲视频一区_国模极品一区二区三区_国产熟女一区二区三区五月婷_亚洲AV成人精品日韩一区18p

              国产精品一区在线播放| 亚洲精品在线观| 久久亚洲一区| 亚洲精品偷拍| 国产亚洲精久久久久久| 欧美大胆人体视频| 欧美在线一二三| 亚洲一区影院| 日韩视频在线免费观看| 一区二区三区中文在线观看 | 国产精品久久国产精品99gif| 国产欧美一区视频| 欧美紧缚bdsm在线视频| 久久久人成影片一区二区三区观看| 亚洲欧洲一区二区三区久久| 国产一区二区三区奇米久涩| 国产精品美女主播| 欧美剧在线观看| 久久婷婷麻豆| 欧美在线观看视频一区二区| 亚洲私人影院在线观看| 日韩亚洲一区在线播放| 在线成人中文字幕| 黄网动漫久久久| 国产一区二区三区久久久| 国产精品丝袜xxxxxxx| 欧美日韩天堂| 欧美日韩极品在线观看一区| 欧美另类视频| 欧美日韩妖精视频| 欧美日韩免费一区二区三区视频| 欧美精品大片| 欧美午夜久久| 国产精品久久看| 国产精品亚洲产品| 国产欧美视频在线观看| 国产美女搞久久| 一区在线视频| 一区视频在线| 99re8这里有精品热视频免费| 一区二区三区四区五区精品| 亚洲一区www| 久久精品夜色噜噜亚洲a∨| 久久久之久亚州精品露出| 欧美高潮视频| 欧美午夜剧场| 国产亚洲欧美日韩一区二区| 在线免费观看日本一区| 亚洲精品一线二线三线无人区| 一区二区三区www| 欧美一区视频| 久久精品国产视频| 久久人人看视频| 欧美欧美天天天天操| 国产欧美一区二区精品婷婷| 亚洲国产精品久久精品怡红院 | 久久蜜桃资源一区二区老牛| 蜜臀av国产精品久久久久| 欧美极品aⅴ影院| 欧美凹凸一区二区三区视频| 久久一区精品| 欧美精品在线一区| 国产亚洲aⅴaaaaaa毛片| 亚洲国产精品一区二区第四页av | 欧美经典一区二区| 国产精品午夜在线观看| 91久久亚洲| 欧美在线视频观看| 欧美日韩三级| 在线电影国产精品| 午夜精品一区二区三区在线视| 久久免费99精品久久久久久| 欧美视频你懂的| 在线观看日韩av电影| 亚洲欧美一区二区三区久久 | 亚洲永久视频| 欧美日韩一卡二卡| 亚洲一区二区免费看| 久久久精品国产免大香伊 | 国产一区二区精品久久91| 最新中文字幕一区二区三区| 欧美在线中文字幕| 国产精品亚洲视频| 亚洲视频专区在线| 欧美高清视频一区| 在线观看日韩精品| 香蕉久久精品日日躁夜夜躁| 欧美性色视频在线| 在线综合亚洲| 欧美日韩一区自拍| av不卡在线观看| 欧美人体xx| 亚洲精品你懂的| 午夜一级久久| 欧美视频一区在线| 亚洲视频日本| 国产精品爱啪在线线免费观看| 亚洲精选一区二区| 欧美日本三级| 一个人看的www久久| 欧美午夜不卡在线观看免费| 一本久久综合亚洲鲁鲁五月天| 欧美日韩1区2区| 中文一区字幕| 国产精品视频内| 久久精品国产久精国产一老狼| 国产免费观看久久黄| 小黄鸭精品密入口导航| 国内精品久久久久影院薰衣草| 久久久久久伊人| 91久久久久久| 欧美日韩国产三级| 亚洲免费一区二区| 国产一本一道久久香蕉| 久久久久国产一区二区三区| 影音先锋亚洲视频| 欧美日韩精品一区二区| 亚洲欧美中文日韩在线| 欧美手机在线| 亚洲欧美综合国产精品一区| 尤物在线精品| 欧美视频在线免费看| 性欧美8khd高清极品| 怡红院av一区二区三区| 欧美另类综合| 久久国内精品视频| 亚洲精品乱码久久久久久久久| 欧美午夜精品久久久久久超碰| 久久riav二区三区| 亚洲免费av观看| 国产亚洲欧美另类中文| 欧美日本在线视频| 久久九九免费| 亚洲一区区二区| 亚洲成人直播| 国产女精品视频网站免费 | 在线看片日韩| 国产精品99免费看 | 激情小说另类小说亚洲欧美| 欧美日韩精品是欧美日韩精品| 久久精品国产视频| 99在线视频精品| 一区二区在线观看av| 国产精品三区www17con| 欧美激情一区二区三区蜜桃视频| 午夜久久久久久| 一区二区不卡在线视频 午夜欧美不卡在 | 久久久xxx| 亚洲综合色网站| 亚洲乱亚洲高清| 136国产福利精品导航网址应用| 国产精品老牛| 欧美日韩中文字幕在线视频| 欧美成人精品一区二区| 国产精品久久97| 久久精品视频一| 亚洲专区国产精品| 99视频日韩| 亚洲人在线视频| 在线播放日韩| 狠狠色2019综合网| 国产亚洲欧美另类一区二区三区| 欧美体内谢she精2性欧美| 欧美精品日韩www.p站| 免费日韩av电影| 牛牛国产精品| 美女精品视频一区| 欧美jjzz| 欧美成人网在线| 欧美高清成人| 欧美激情免费观看| 欧美大胆成人| 欧美日本二区| 欧美日韩在线不卡| 欧美人与禽猛交乱配视频| 欧美大片在线观看一区二区| 久热国产精品| 模特精品裸拍一区| 久久久久久网址| 免费亚洲婷婷| 欧美日韩国产123区| 欧美日韩情趣电影| 欧美日韩一二区| 女人天堂亚洲aⅴ在线观看| 老牛嫩草一区二区三区日本| 久久久精品一区二区三区| 久久九九有精品国产23| 蜜臀av在线播放一区二区三区| 免费在线一区二区| 欧美日在线观看| 国产欧美va欧美va香蕉在| 激情视频一区| 一区二区不卡在线视频 午夜欧美不卡在 | 亚洲影院免费观看| 久久精品视频在线看| 欧美韩日一区| 国产精品扒开腿做爽爽爽视频| 国产一区二区久久精品| 激情欧美一区二区| 一区二区日韩免费看|