YAL - Yacine's & Anthony Programming Language

YAL is an interpreted programming language created as a part of the Compiler Construction course during CYBERUS Masters module using javaCC & jjtree, the aim was to create a simple language that beginners can use to get started. This is why we inspired the syntax from Pascal the first programming language I learned in university

How to use

1. Clone the repo
2. Have javacc jjtree and optionally dot installed
3. use the PowerShell script build.ps1 to build the compiler it will generate yalc.jar file
4. run the compiler on your code using java -jar yalc.jar yourfile.txt

Basic Introduction to YAL

This README provides a very basic introduction to YAL programming language, covering some fundamental concepts such as variables, functions, if statements, and while loops.

Overall Structure

program programName
// function declaration first (this is enforced)
// procedure declartion 
var
// variables declaration 
begin 
	// statements
end

Variables and Their Types

In YAL, a variable must be declared before it can be used in the variables declaration section. Each variable has a specific type, which determines the size and layout of the variable's memory, as well as the range of values that can be stored within that memory.

var     
number: int;     
name: string;     
isAvailable: bool;     
price: real;

Here, number is an integer variable, name is a string, isAvailable is a boolean, and price is a real (floating-point) variable.

Functions and Function Returns Using Result Variable

Functions in YAL are blocks of code that carry out specific tasks and can return a value. The Result variable is used in functions to hold the value that the function will return. functions have there own variables declaration sections

function AddNumbers(a:int, b: int): int
// optional variables declaration section
// var
// x:int;
begin     
Result := a + b; 
end

This function, AddNumbers, takes two integers a and b, adds them, and returns the result.

Procedures

Procedures in YAL are blocks of code that are designed to perform a specific task, but unlike functions, they do not return a value. Procedures are useful for executing code that performs actions, such as printing to the screen, calculating results, or modifying variables, without needing to return a result.

Here's a simple example of a procedure:

procedure DisplayGreeting(name: string)
begin     
	print("hello, " + name); 
end

In this example, the DisplayGreeting procedure takes a single parameter, name, and prints a personalized greeting message.

Calling a Procedure

To use a procedure, you simply call it by its name followed by parentheses. If the procedure takes parameters, you provide the values within the parentheses.

begin     
DisplayGreeting('Alice'); 
end

If Statement

The if statement is used for conditional execution. YAL executes the code inside the if statement only if the condition is true.

var     
age: int; 
begin     
	age := 20;     
	if age >= 18 then     
	begin         
		print('You are an adult.');     
	end
	else
	begin
		// something else 
	end
end

This will output "You are an adult." because age is greater than or equal to 18.

While Statement

The while statement allows you to repeat a block of code as long as a certain condition is true.

var     
count: int; 
begin     
	count := 1;     
	while count <= 5 do     
	begin         
		print('Count: ', count);
		count := count + 1;
	end
end

This will print the numbers from 1 to 5.

Arithmetic and boolean expression*

Built-in functions

print

same as System.out.prinln in java

readInt

this function will keep asking the user to input an int until an int is received

readString

receives a string from the user on fail it returns null

Semantic Analysis

We detect most semantic errors, either inside nested operations, like ifs and whiles, or outside them.. For displaying these errors we indicate the line, variable and type of error. Errors we detect range from:

1. Function-related Errors:
   • Duplicate functions: Declaring functions with the same name. (func_duplicate.pas)
   • Duplicate identifier: Declaring functions with the same name as another identifier such as a function name, variable name or procedure name. (func_dupe_ident.pas)
   • Function type mismatch: Mismatch between declared and actual types in function definitions. (func_type_mism.pas)
   • Function no return: function does not return anything when it should: this will return null. (func_not_return.pas)
   • Function not declared: Calling a function that hasn't been declared. (func_not_declared.pas)
   • Wrong number of arguments for a function: Incorrect number of parameters passed to a function. (func_wrong_arg_num.pas)
   • Wrong type of arguments: Mismatch in the type of arguments passed to a function. (func_wrong_arg_type.pas)
   • Return type not declared: Missing declaration of the return type for a function. (func_ret_type_not_declared.pas)
   • Return type mismatch: Mismatch between the declared and actual return types of a function. (func_ret_type_mism.pas)
   • Argument not initialized: giving a function a variable that has not been initialized. (func_arg_not_init.pas)
2. . Procedure-related Errors:
   • Duplicate procedure: Declaring procedure with the same name. (proc_duplicate.pas)
   • Duplicate identifier: Declaring procedure with the same name as another identifier such as a function name, variable name or procedure name. (proc_dupe_ident.pas)
   • procedure type mismatch: Mismatch between declared and actual types in procedure definitions. (proc_type_mism.pas)
   • procedure not declared: Calling a procedure that hasn't been declared. (proc_not_declared.pas)
   • Wrong number of arguments for a procedure: Incorrect number of parameters passed to a procedure. (proc_wrong_arg_num_1(2).pas)
   • Wrong type of arguments: Mismatch in the type of arguments passed to a procedure. (proc_wrong_arg_type.pas)
   • Argument not initialized: giving a procedure a variable that has not been initialized. (proc_arg_not_init.pas)
3. Argument and Parameter Errors:
   • Undefined arguments: Use of arguments that haven't been defined. (undefined_arg.pas)
4. Variable-related Errors:
   • Type mismatches: Inconsistencies between declared and assigned types of variables. (type_mismatch.pas)
   • Duplicate variables: In the same scope, declaring variables with the same name or with a name of another identifier such as a function or a procedure. (dupe_variable.pas)
   • Undefined variables: Using variables that haven’t been defined. (undefined_variable.pas)

• Expression-Related Errors:
  • Arithmetic Type Mismatch: Performing arithmetic operations on incompatible types, except for certain cases like int and real (int gets casted to real). (arth_type_mism.pas)
  • Comparison Type Mismatch: Comparing values of different types, with exceptions for int and double. (comp_type_mism.pas)
  • Invalid Boolean Operations: Using logical boolean operators (like AND, OR) on non-boolean types. (invalid_bool_ops.pas)
  • Division by Zero: Attempting to divide a number by zero, which is undefined. (div_by_zero.pas)

Limitations

• Can not call a function within an expression
• Variable Types: Supported variable types are: integer (int), real number (real), string (string), and boolean (boolean). no null type, null is not recognized.
• Variable Declaration: Declaration of multiple variables in a single line using comma separation is not allowed. This simplification helps in the implementation of the Abstract Syntax Tree (AST) for variable declarations.
• Function Calls in Parameters: When calling a function, only values or variable names can be used as parameters. Function calls within parameters are not permitted.
• Semantic Analysis: Semantic analysis occurs at runtime. Therefore, functions with semantic errors can be declared without immediate detection. These errors become apparent only when the function is called. This could be improved by implementing separate visitors for semantic analysis and code generation.
• Nested Functions and Procedures: Nested functions and procedures are not allowed.
• Function Calls in Expressions: Functions cannot be called within arithmetic expressions