Understanding Backus Nauer Form (BNF) Syntax
The scripts used by the ATL Registrar are described in this topic using BNF syntax, which uses the notation shown in the following table.
|
Convention/symbol |
Meaning |
|---|---|
|
::= |
Equivalent |
|
| |
OR |
|
X+ |
One or more Xs. |
|
[X] |
X is optional. Optional delimiters are denoted by []. |
|
Any bold text |
A string literal. |
|
Any italicized text |
How to construct the string literal. |
As indicated in the preceding table, registrar scripts use string literals. These values are actual text that must appear in your script. The following table describes the string literals used in an ATL Registrar script.
|
String literal |
Action |
|---|---|
|
ForceRemove |
Completely removes the next key (if it exists) and then re-creates it. |
|
NoRemove |
Does not remove the next key during Unregister. |
|
val |
Specifies that <Key Name> is actually a named value. |
|
Delete |
Deletes the next key during Register. |
|
s |
Specifies that the next value is a string (REG_SZ). |
|
d |
Specifies that the next value is a DWORD (REG_DWORD). |
|
m |
Specifies that the next value is a multistring (REG_MULTI_SZ). |
|
b |
Specifies that the next value is a binary value (REG_BINARY). |