Bug 6002: In SCT showing only a single flag in the flag legend prevents SCT from opening
Bug Number: 6002
Release notes (y/n): Yes
For Release Nums: 7.1.2

This problem was caused by an unnecessary ambiguity in the SCT serialization's 
Flex/Bison grammar.  We make use of both QUOTED_CHAR_TOKEN and 
QUOTED_STRING_TOKEN token definitions.  The intention was to follow the 
"C-language" convention of quoted characters using Single-Quote characters 
and quoted strings using Double-Quote characters.  However, the Single-Quote 
rule was allowing ALSO use of double quotes, with these definitions 
(in QtSCT/SctFile.l) -- the "lex" (i.e. "flex") file:

   quoted_char    (\"[^\"]\")|('[^']')
   quoted_string  \"[^\"]*\"

(Notice the vertical bar in the first definition above -- "or" -- matching 
either the formula to the left or the formula to the right).  That hybrid 
rule was causing source strings such as "T" (delimited with double-quotes) 
to be recognized as a quoted_char (QUOTED_CHAR_TOKEN) instead of a 
quoted_string (QUOTED_STRING_TOKEN).

That messed up the interpretation of the last line in this SCT serialization 
excerpt. (Typically that quoted string is more than one character):

  ... ... ...
  TOOLBAR_START_RUN       True
  TOOLBAR_FLAGS           True
  TOOLBAR_FLAG_BUT_CODES  "T"
  ... ... ...

Changing the first definition in SctFile.l as follows fixed the problem:

   quoted_char    '[^']'
   quoted_string  \"[^\"]*\"

Note that, after editing SctFile.l or SctFile.y, I just "source" the 
"doMakeBison" file in QtSCT -- and notice if errors are reported.  (I do 
this on Alamosa (Linux machine), but I believe we know that this works in a 
Windows terminal, making use of UnxUtils commands).  That generates the 
lex.sct_file_.cpp and SctFile.tab.cpp files, which are under source control 
(GIT), i.e. as RiverWare source.

---