Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
preprocessor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Dynare
preprocessor
Commits
73f71862
Commit
73f71862
authored
6 years ago
by
Houtan Bastani
Browse files
Options
Downloads
Patches
Plain Diff
doc: macroprocessor: clarify statements on macro functions
parent
3776e3b8
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/macroprocessor/macroprocessor.tex
+6
-2
6 additions, 2 deletions
doc/macroprocessor/macroprocessor.tex
with
6 additions
and
2 deletions
doc/macroprocessor/macroprocessor.tex
+
6
−
2
View file @
73f71862
...
...
@@ -95,13 +95,17 @@
\frametitle
{
Variables
}
\begin{itemize}
\item
The macro processor has its own list of variables which are different than model variables and MATLAB/Octave variables
\item
There are
5
types of macro-variables:
\item
There are
4
types of macro-variables:
\begin{itemize}
\item
integer
\item
string (declared between
\textit
{
double
}
quotes)
\item
integer array
\item
string array
\item
string function
\end{itemize}
\item
Macro-Functions are also supported
\begin{itemize}
\item
only accept string aruments
\item
must evaluate to a string
\end{itemize}
\item
No boolean type:
\begin{itemize}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment