jEdit
4. Notes and Limitations
4.1 Sentaurus Process Mode and Sentaurus Interconnect Mode
4.2 Sentaurus Device Mode
Objectives
- To provide information about the limitations of the Sentaurus Process mode,
Sentaurus Interconnect mode, and Sentaurus Device mode.
4.1 Sentaurus Process Mode and Sentaurus Interconnect Mode
Syntax highlighting is activated only when certain additional conditions (not
imposed by Sentaurus Process or Sentaurus Interconnect) are met:
- Placement of the equal sign: No space between the keyword and the equal sign,
and at least one space between the equal sign and the value:
- name= mask6 (highlight)
- name = mask6 (no highlight)
- name=mask6 (no highlight)
- Two conditions after the hash (#):
- #header (highlight as a Sentaurus Workbench variable)
- #this is a comment line (highlight as a comment line)
- Aliases and abbreviations are commonly not highlighted:
- location= (highlight)
- loc= (no highlight)
Figure 1. Syntax highlighting in
Sentaurus Process. (Click image for full-size view.)
4.2 Sentaurus Device Mode
Syntax highlighting is activated only when certain additional conditions (not imposed
by Sentaurus Device) are met:
- Two conditions after the hash (#):
- #header (highlight as a Sentaurus Workbench variable)
- #this is a comment line (highlight as a comment line)
- Sentaurus Device accepts certain abbreviations and tolerates certain misspelled
keywords. However, aliases and abbreviations are commonly not highlighted:
- EffectiveIntrinsicDensity (highlight)
- EffectiveIntrinsicDen (no highlight)
- Keywords are context sensitive, that is, a keyword will be highlighted only
if it appears inside the section to which it belongs. For example, SRH
will be highlighted in the Recombination() section but not in the
Mobility() section. Therefore, the parts of the code that do not have
highlighting potentially follow incorrect syntax.
A separate mode for the parameter files of Sentaurus Device (.par)
is available as well. The mode simply describes the general file structure and
ensures that indentation is correct. No special keywords are coded; therefore,
command completion is very limited.
Copyright © 2017 Synopsys, Inc. All rights reserved.