Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
dynare
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
Frédéric Karamé
dynare
Commits
20b51b3c
Commit
20b51b3c
authored
6 years ago
by
Johannes Pfeifer
Browse files
Options
Downloads
Patches
Plain Diff
Document treatment of several Matlab statements in one line
Related to #1637
parent
5c75c301
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/dynare.texi
+13
-0
13 additions, 0 deletions
doc/dynare.texi
with
13 additions
and
0 deletions
doc/dynare.texi
+
13
−
0
View file @
20b51b3c
...
...
@@ -1105,6 +1105,13 @@ it did not expect. Hence, it throws an error of the form: @code{ERROR:
PARAMETERS}. In this case, you would simply place a semicolon at the
end of line one and the parser would continue processing.
It is also helpful to keep in mind that any piece of code that does not violate
Dynare syntax, but at the same time is not recognized by the parser, is interpreted
as native Matlab code. This code will be directly passed to the @code{driver.m}-file.
Investigating @code{driver.m}-file then helps with debugging. Such problems most often
occur when defined variable or parameter names have been misspelled so that Dynare's
parser is unable to recognize them.
@node The Model file
@chapter The Model file
...
...
@@ -1143,6 +1150,12 @@ A model file contains a list of commands and of blocks. Each command
and each element of a block is terminated by a semicolon
(@code{;}). Blocks are terminated by @code{end;}.
If Dynare encounters an unknown expression at the beginning of a line or after a semicolon,
it will parse the rest of that line as native Matlab code, even if there are
more statements separated by semicolons present. To prevent cryptic error
messages, it is strongly recommended to always only put one statement/command
into each line and start a new line after each semicolon.
Most Dynare commands have arguments and several accept options,
indicated in parentheses after the command keyword. Several options
are separated by commas.
...
...
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