日本欧洲视频一区_国模极品一区二区三区_国产熟女一区二区三区五月婷_亚洲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

              在线观看91精品国产入口| 久久全球大尺度高清视频| 国产精品久久久久久久久久免费看| 亚洲一区二区在线观看视频| 一区二区三区在线观看欧美 | 亚洲香蕉视频| 国内免费精品永久在线视频| 欧美www视频在线观看| 夜夜爽www精品| 国户精品久久久久久久久久久不卡 | 蜜乳av另类精品一区二区| 亚洲图片欧美午夜| 亚洲精品国产视频| 1024成人网色www| 国产欧美一区二区三区在线老狼| 欧美黄免费看| 欧美成人国产| 狂野欧美激情性xxxx| 亚洲一级二级| 亚洲激情校园春色| 精品动漫3d一区二区三区免费| 欧美激情导航| 久久影音先锋| 欧美一区二区三区在线视频| 亚洲毛片在线看| 国内精品模特av私拍在线观看| 欧美三级特黄| 欧美午夜在线观看| 欧美日韩中文字幕在线| 欧美精品国产精品| 久久嫩草精品久久久久| 亚洲精品国产精品乱码不99按摩 | 欧美一区二区高清| 亚洲蜜桃精久久久久久久| 国产视频一区三区| 国产精品视频yy9299一区| 欧美视频在线观看免费| 欧美日韩国产精品自在自线| 欧美成人亚洲成人日韩成人| 欧美精品在线一区| 欧美婷婷六月丁香综合色| 欧美区一区二| 欧美人与禽性xxxxx杂性| 免费不卡亚洲欧美| 麻豆精品精品国产自在97香蕉| 午夜精品影院| 久久av二区| 久久久91精品| 99re66热这里只有精品3直播| 国产视频久久久久久久| 一区二区三区在线看| 在线精品福利| 99精品免费| 久久av一区二区三区| 美腿丝袜亚洲色图| 国产精品九九| 悠悠资源网久久精品| 亚洲乱码国产乱码精品精| 亚洲影院在线| 久久五月激情| 国产精品男女猛烈高潮激情 | 国产亚洲美州欧州综合国| 亚洲高清av在线| 亚洲视频精品在线| 久久中文欧美| 国产欧美一区二区三区另类精品| 黄色亚洲大片免费在线观看| 一区二区三区欧美| 久热精品视频在线免费观看| 欧美性事免费在线观看| 亚洲国产你懂的| 欧美在线国产| 国产精品久久波多野结衣| 红桃av永久久久| 亚洲欧美视频一区二区三区| 欧美3dxxxxhd| 伊人春色精品| 久久成人综合网| 欧美午夜不卡在线观看免费 | 在线日韩电影| 久久精品国产亚洲精品| 国产精品美女久久久久久免费 | 欧美插天视频在线播放| 国产欧美视频一区二区三区| 在线视频你懂得一区| 国产亚洲欧美日韩日本| 欧美日韩亚洲一区二区三区在线| 久久精品国产精品亚洲综合| 国产精品爱久久久久久久| 亚洲激情一区| 欧美成年视频| 亚洲大黄网站| 免费成人av在线| 黄色亚洲免费| 久久精品综合网| 国产亚洲欧美日韩在线一区| 久久se精品一区二区| 国产精品国产三级国产专播品爱网 | 欧美尤物一区| 国产亚洲欧美一区二区| 午夜宅男久久久| 国产乱肥老妇国产一区二| 中文日韩在线| 欧美深夜福利| 亚洲在线中文字幕| 国产精品激情电影| 亚洲女同精品视频| 国产精品一区免费视频| 午夜精品影院在线观看| 国产日韩精品一区二区三区 | 国产午夜久久| 麻豆精品一区二区av白丝在线| 激情欧美丁香| 欧美成人综合| 亚洲永久免费| 国内精品久久久久久| 久久野战av| av不卡免费看| 国产午夜精品久久久| 裸体丰满少妇做受久久99精品| 亚洲人成77777在线观看网| 欧美精品一区二区三区视频| 在线精品一区| 欧美国产第二页| 制服丝袜亚洲播放| 国产日韩欧美一区在线| 麻豆成人精品| 亚洲视频福利| 在线观看日韩www视频免费| 欧美精品一区在线发布| 亚洲中字黄色| 黄色小说综合网站| 欧美日韩一区二区欧美激情| 亚洲欧美高清| 亚洲国产欧美在线| 国产欧美日韩另类视频免费观看 | 欧美一区日韩一区| 亚洲毛片一区| 国产在线高清精品| 欧美日本久久| 美日韩精品视频免费看| 亚洲免费中文| 亚洲日韩欧美一区二区在线| 国产一区二区三区电影在线观看| 欧美国产欧美亚洲国产日韩mv天天看完整| 亚洲视频国产视频| 亚洲人成网站999久久久综合| 国产精品普通话对白| 欧美大片在线观看一区| 久久久噜噜噜久久中文字幕色伊伊 | 国产精品美女诱惑| 欧美日本不卡视频| 久久综合久久88| 久久国产精品99久久久久久老狼| 在线综合亚洲| 91久久精品国产91久久| 一区在线观看| 国产日韩欧美视频在线| 国产精品捆绑调教| 欧美午夜理伦三级在线观看| 欧美日韩成人一区二区| 欧美成熟视频| 欧美二区视频| 蜜桃精品久久久久久久免费影院| 久久福利资源站| 午夜视频在线观看一区二区| 亚洲视频第一页| 亚洲一级黄色av| 亚洲伊人观看| 欧美一区二区成人6969| 亚洲欧美在线一区二区| 亚洲男人第一网站| 午夜视频在线观看一区| 欧美专区第一页| 久久久精品999| 久久久亚洲人| 欧美精品色一区二区三区| 欧美精品www在线观看| 欧美日韩国产经典色站一区二区三区| 欧美成人久久| 欧美日韩国产一区二区三区地区 | 亚洲黄色有码视频| 99亚洲精品| 亚洲综合导航| 久久国产福利| 欧美高清免费| 欧美日韩国产天堂| 国产精品五区| 樱桃国产成人精品视频| 亚洲人成高清| 欧美一区久久| 欧美成人a视频| 国产精品电影观看| 国产自产v一区二区三区c| 在线观看亚洲a| 夜久久久久久| 久久久久九九九| 欧美天堂在线观看| 黄色日韩精品| 中文国产一区|