further cutting

1 files changed, 1 insertions, 7 deletions

diff --git a/report/esoteric_project_report.tex b/report/esoteric_project_report.tex
index 5b33d6b..79cd596 100644
--- a/report/esoteric_project_report.tex
+++ b/report/esoteric_project_report.tex
@@ -100,13 +100,7 @@ Esolangs are programming languages designed to be jokes or proof of concept lang
 There are many different examples of esoteric languages. 
 One such language is the Shakespearian Programming Language, which is an  where code is written so it reads like how a script would, such as \texttt{[Enter Juliet]} where \texttt{Juliet} may be a variable name. 
 Another example of an esoteric language is Befunge, one of the most popular and well known esoteric languages, which is intentionally designed to be hard to compile. 
-Befunge code is written in a 2d plane, where ASCII characters represent instructions. 
-An instruction pointer starts in the top left of this plane, and begins travelling right.
-Data is stored in a stack, similar to many other esoteric languages. 
-One other feature of Befunge is that it is self-modifying, meaning instructions can modify the plane the code is on.
-Since Befunge-98, there is no fixed size of the plane, meaning Befunge is a Turing complete language. 
-Moreover, Pyth is a language designed to be both concise, but also clear to read. 
-Pyth is designed to be similar to python, but with every instruction a single character. When ran, a pyth code is first compiled into python before being executed. Unlike many other esoteric languages, Pyth is procedural based, not stack based. Print statements are also implicit in Pyth, and all constructs are end of line terminated.
+Moreover, Pyth is yet another esoteric language that is designed to be similar to python, but with every instruction a single character. When ran, a pyth code is first compiled into python before being executed. 
 
 \chapter{Compiler Design and Methodology}
 This chapter will discuss how compilers work, and the design behind them. The goal of a compiler is to convert the source code into an from which the CPU can execute. As mentioned in chapter 2, a compiler works by converting the entire source code in one go, then executing, unlike a interpreter which executes each line at a time. However, before the code can be executed a number of steps have to be taken.