Skip to content

Commit

Permalink
Comma Before according to review
Browse files Browse the repository at this point in the history
  • Loading branch information
HansOlsson committed Jan 10, 2023
1 parent 51635ce commit ffdb7ba
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion chapters/classes.tex
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ \subsection{Syntax}\label{component-declaration-syntax}\label{syntax-and-example

\begin{nonnormative}
The declaration of a component states the type, access, variability, data flow, and other properties of the component.
A \lstinline[language=grammar]!component-clause! i.e., the whole declaration, contains type prefixes followed by a \lstinline[language=grammar]!type-specifier! with optional \lstinline[language=grammar]!array-subscripts! followed by a \lstinline[language=grammar]!component-list!.
A \lstinline[language=grammar]!component-clause!, i.e., the whole declaration, contains type prefixes followed by a \lstinline[language=grammar]!type-specifier! with optional \lstinline[language=grammar]!array-subscripts! followed by a \lstinline[language=grammar]!component-list!.

There is no semantic difference between variables declared in a single declaration or in multiple declarations.
For example, regard the following single declaration (\lstinline[language=grammar]!component-clause!) of two matrix variables:
Expand Down
2 changes: 1 addition & 1 deletion chapters/interface.tex
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ \section{The Concepts of Type, Interface and Subtype}\label{the-concepts-of-type

A \emph{type} can conceptually be viewed as a \emph{set of values}. When
we say that the variable \lstinline!x! has the type \lstinline!Real!, we mean that the value of
\lstinline!x! belongs to the set of values represented by the type \lstinline!Real! i.e.,
\lstinline!x! belongs to the set of values represented by the type \lstinline!Real!, i.e.,
roughly the set of floating point numbers representable by \lstinline!Real!, for the
moment ignoring the fact that \lstinline!Real! is also viewed as a class with
certain attributes. Analogously, the variable \lstinline!b! having \lstinline!Boolean! type
Expand Down
2 changes: 1 addition & 1 deletion chapters/packages.tex
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ \subsection{Rules for Import-Clauses}\label{summary-of-rules-for-import-clauses}
The \emph{order} of \lstinline!import!-clauses does not matter.
\item
One can only import \emph{from} packages, not from other kinds of classes.
Both packages and classes can be imported \emph{into} i.e., they may contain \lstinline!import!-clauses.
Both packages and classes can be imported \emph{into}, i.e., they may contain \lstinline!import!-clauses.
\item
An imported package or definition should always be referred to by its fully qualified name in the \lstinline!import!-clause.
\item
Expand Down

0 comments on commit ffdb7ba

Please sign in to comment.