From b49bb78db545f0aa6569d8e78e79d4740ca77c4a Mon Sep 17 00:00:00 2001
From: Alfie Eagleton <67986414+TheAlfanator@users.noreply.github.com>
Date: Sun, 17 Oct 2021 17:53:14 +0100
Subject: Chapter 3 - FORTRAN

Created a grammar table regarding FORTRAN and Java.
---
 report/esoteric_project_report.tex | 66 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 66 insertions(+)

(limited to 'report/esoteric_project_report.tex')

diff --git a/report/esoteric_project_report.tex b/report/esoteric_project_report.tex
index 8306b94..055f752 100644
--- a/report/esoteric_project_report.tex
+++ b/report/esoteric_project_report.tex
@@ -79,6 +79,72 @@ Esolangs are programming languages designed to be jokes or proof of concept lang
 \section{Example - Shakespearian Programming Language}
 The Shakespeare Programming Language is esoteric code parodied on extracts from Romeo and Juliet. Here, code is written so it reads like how a script would, such as \texttt{[Enter Juliet]} where \texttt{Juliet} may be a variable name. Other examples include using \texttt{Acts} or \texttt{Scenes} as GOTO statements, where the interpreter can jump to a certain point in the code and read from there. Otherwise, these are ignored similar to the title or character descriptions. Other examples include LOLCODE, Hodor or White Space. This serves the purpose of writing code in a different manner to usual, sometimes for humour. The aim is to replace typical language features so that it can still be read by a compiler or interpreter but also look and read very differently by the user.  
 
+\chapter{Grammar - FORTRAN}
+
+\section {Why we chose FORTRAN}
+
+asdf
+
+\begin{table}[h!]
+	\begin{center}
+		
+		\begin{tabular}{|l|r|}
+			\hline
+			\textbf{Token} & \textbf{Replaces}\\
+			\hline
+			! & \slash\slash \\
+			\hline
+			PROGRAM x & public class x \{ \\
+			\hline
+			END PROGRAM & \} \\
+			\hline
+			INTEGER & int \\
+			\hline
+			LOGICAL & boolean \\
+			\hline
+			.FALSE. & false \\
+			\hline
+			.TRUE. & true \\
+			\hline
+			CHARACTER(LEN=x) & String \\
+			\hline
+			:: & = \\
+			\hline
+			IF (x) THEN & if(x) \{ \\
+			\hline
+			ELSE & else \\
+			\hline
+			END IF & \} \\
+			\hline
+			SELECT CASE (x) & switch(x) \{ \\
+			\hline
+			CASE (x) & case x: \\
+			\hline
+			CASE DEFAULT & default: \\
+			\hline
+			END SELECT & \} \\
+			\hline
+			x & x; \\
+			\hline
+			DO x = y, z & for(x = y, x < z; x++) \{ \\
+			\hline
+			END DO & \} \\
+			\hline
+			PRINT *, x & System.out.println(x); \\
+			\hline
+			SUBROUTINE x & static void x() \{ \\
+			\hline
+			END SUBROUTINE & \} \\
+			\hline
+			CALL x & x(); \\
+			\hline
+		
+		\end{tabular}
+		\label{tab:table1}
+		\caption{Grammar table for Fortran}
+	\end{center}
+\end{table}
+
 \chapter{Methodology}\label{MethLab}
 
 Describe here various methods that will be used in your project. Use different sections for distinctly different subjects and use subsections for specific details on the same subject. Only use subsubsections or paragraphs (which are not numbered) if you believe this is really necessary. Since implementation will happen in sprints, this section may need several updates with parts being added and deleted across the project.
-- 
cgit v1.2.3

