ICODE-ADC/lammps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@3731 f3b2605a-c512-4ea7-a41b-209d697bcdaa

Browse Source
This commit is contained in:
sjplimp
2010-01-19 20:04:41 +00:00
parent fae7fd7621
commit 60908cc6c5
8 changed files with 188 additions and 164 deletions
Download Patch File Download Diff File Expand all files Collapse all files

45
doc/Section_commands.html
View File

@ -84,25 +84,27 @@ file names or user-chosen ID strings.
</P>
<P>Here is how each line in the input script is parsed by LAMMPS:
</P>
<P>(1) If the line ends with a "&" character (the "and" character which
is shift-7 on most keyboards) with no trailing whitespace (and no
surrounding quotes), the command is assumed to continue on the next
line. The next line is concatenated to the previous line by removing
the "&" character ("and" character) and newline. This allows long
commands to be continued across two or more lines.
<P>(1) If the last printable character on the line is a "&" character
(with no surrounding quotes), the command is assumed to continue on
the next line. The next line is concatenated to the previous line by
removing the "&" character and newline. This allows long commands to
be continued across two or more lines.
</P>
<P>(2) All characters from the first "#" character onward are treated as
comment and discarded.
comment and discarded. See an exception in (6). Note that a
comment after a trailing "&" character will prevent the command from
continuing on the next line. Also note that for multi-line commands a
single leading "#" will comment out the entire command.
</P>
<P>(3) The line is searched repeatedly for $ characters which indicate
variables that are replaced with a text string. If the $ is followed
by curly brackets, then the variable name is the text inside the curly
brackets. If no curly brackets follow the $, then the variable name
is the character immediately following the $. Thus ${myTemp} and $x
refer to variable names "myTemp" and "x". See the
<A HREF = "variable.html">variable</A> command for details of how strings are
assigned to variables and how they are substituted for in input
scripts.
<P>(3) The line is searched repeatedly for $ characters, which indicate
variables that are replaced with a text string. See an exception in
(6). If the $ is followed by curly brackets, then the variable name
is the text inside the curly brackets. If no curly brackets follow
the $, then the variable name is the single character immediately
following the $. Thus ${myTemp} and $x refer to variable names
"myTemp" and "x". See the <A HREF = "variable.html">variable</A> command for
details of how strings are assigned to variables and how they are
substituted for in input script commands.
</P>
<P>(4) The line is broken into "words" separated by whitespace (tabs,
spaces). Note that words can thus contain letters, digits,
@ -111,11 +113,12 @@ underscores, or punctuation characters.
<P>(5) The first word is the command name. All successive words in the
line are arguments.
</P>
<P>(6) Text with spaces can be enclosed in double quotes so it will be
treated as a single argument. See the <A HREF = "dump_modify.html">dump modify</A>
or <A HREF = "fix_print.html">fix print</A> commands for examples. A '#' or '$'
character that is in text between double quotes will not be treated as
a comment or substituted for as a variable.
<P>(6) If you want text with spaces to be treated as a single argument,
it can be enclosed in double quotes. The quotes are removed when the
single argument is stored in its final form. See the <A HREF = "dump_modify.html">dump modify
format</A> or <A HREF = "if.html">if</A> commands for examples. A "#"
or "$" character that is between double quotes will not be treated as
a comment indicator in (2) or substituted for as a variable in (3).
</P>
<HR>