Skip to content

Update function definitions #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tefu wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update function definitions #23

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8d76710
Update parameter definitions
tefu Apr 22, 2016
8f9b6f9
Create definition for function overloading
tefu Apr 22, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 16 additions & 2 deletions CPSL.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -381,10 +381,24 @@ \subsection{For}
Either in an monotonically increasing or decreasing fashion depending on whether the keyword to or downto was used. For each value of the new variable a list of statements is executed.
\section{Function and Procedure Calls}
\subsection{Parameters}
Parameters in CPSL are always passed by value.
No function or procedure can have side effects, except for output or through global variables.
Parameters in CPSL can be passed by either value or reference. To be passed by
reference, a parameter must be a variable. No function or procedure can have
side effects, except for output or through global variables and reference
parameters.
\subsection{Return}
The return statement passes control back to a function or procedure caller. If it is a function the expression returned becomes the expression of the function call in the callers scope.
\subsection{Function Overloading}
Functions or procedures with different bodies may have the same name. For this
to be valid, each function/procedure must have a different type signature. A type
signature is defined by the order of parameters and their respective types. Note
that,

\begin{itemize}
\item The parameter names do not affect a function's type signature.
\item \textbf{var}/\textbf{ref} does not change a function's type signature.
\item The return type also does not affect a function's type signature.
\end{itemize}

\section{User Defined Types}
\subsection{Arrays}
Arrays are a contiguously allocated, homogeneously typed set of variables.
Expand Down