Skip to content
Snippets Groups Projects
Commit d7a5f50b authored by Christophe Geuzaine's avatar Christophe Geuzaine
Browse files

*** empty log message ***

parent 018b1f48
No related branches found
No related tags found
No related merge requests found
...@@ -360,7 +360,7 @@ int MergeFile(const char *name, int warn_if_missing) ...@@ -360,7 +360,7 @@ int MergeFile(const char *name, int warn_if_missing)
CTX.geom.draw = 1; CTX.geom.draw = 1;
if(!strncmp(header, "$PTS", 4) || !strncmp(header, "$NO", 3) || if(!strncmp(header, "$PTS", 4) || !strncmp(header, "$NO", 3) ||
!strncmp(header, "$PARA", 5) || !strncmp(header, "$ELM", 4) || !strncmp(header, "$PARA", 5) || !strncmp(header, "$ELM", 4) ||
!strncmp(header, "$MeshFormat", 11)) { !strncmp(header, "$MeshFormat", 11) || !strncmp(header, "$Comments", 9)) {
status = model->readMSH(name); status = model->readMSH(name);
#if !defined(HAVE_NO_POST) #if !defined(HAVE_NO_POST)
if(status > 1) status = PView::readMSH(name); if(status > 1) status = PView::readMSH(name);
......
...@@ -549,8 +549,8 @@ preceding rule. ...@@ -549,8 +549,8 @@ preceding rule.
@findex /*, */ @findex /*, */
@findex // @findex //
All parsed input files (@file{.geo}, @file{.pos}) support both C and C++ All parsed input files (@file{.geo}) support both C and C++ style
style comments: comments:
@enumerate @enumerate
@item @item
...@@ -563,9 +563,10 @@ These commands won't have the described effects inside double quotes or ...@@ -563,9 +563,10 @@ These commands won't have the described effects inside double quotes or
inside keywords. Also note that `white space' (spaces, tabs, new line inside keywords. Also note that `white space' (spaces, tabs, new line
characters) is ignored inside all expressions. characters) is ignored inside all expressions.
You can add comments in a mesh file (@file{.msh}) by creating a section You can add comments in a mesh file (@file{.msh}) by adding a section
with an unrecognized label (e.g. @code{$Comments}/@code{$EndComments}): with an unrecognized label (e.g., @code{$Comments}/@code{$EndComments})
see @ref{MSH ASCII file format}. after the @code{$MeshFormat}/@code{$EndMeshFormat} section: see @ref{MSH
ASCII file format}.
@c ========================================================================= @c =========================================================================
@c General tools @c General tools
...@@ -2992,7 +2993,8 @@ information about the file (@code{$MeshFormat}), followed by several ...@@ -2992,7 +2993,8 @@ information about the file (@code{$MeshFormat}), followed by several
optional sections defining the nodes (@code{$Nodes}), elements optional sections defining the nodes (@code{$Nodes}), elements
(@code{$Elements}), region names (@code{$PhysicalName}) and (@code{$Elements}), region names (@code{$PhysicalName}) and
post-processing datasets (@code{$NodeData}, @code{$ElementData}, post-processing datasets (@code{$NodeData}, @code{$ElementData},
@code{$ElementNodeData}). Sections can be repeated in the same file, and @code{$ElementNodeData}). Any section with an unrecognized header is
simply ignored. Sections can be repeated in the same file, and
post-processing sections can be put into separate files (e.g. one file post-processing sections can be put into separate files (e.g. one file
per time step). per time step).
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment