boolean option processing
Option parsing for booleans tried to accept "optname:true" or "optname:yes" or "optname:false" or "optname:no" but it didn't work because boolean options with a value were rejected before getting to that. Make parsing for booleans get far enough to handle those values, treat them as case-insensitive, and add "on" and "off" as additional choices. "true" and "false" can be truncated to 3 letters, the other values need to be fully spelled out but are all only 2 or 3 letters long.
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
$NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.230 $ $NHDT-Date: 1591195832 2020/06/03 14:50:32 $
|
||||
$NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.231 $ $NHDT-Date: 1591476281 2020/06/06 20:44:41 $
|
||||
|
||||
General Fixes and Modified Features
|
||||
-----------------------------------
|
||||
@@ -363,6 +363,8 @@ new objects: amulets of flying and guarding
|
||||
new monsters: displacer beast ('f') and genetic engineer ('Q')
|
||||
make camera flash which reveals previously unseen map features or objects or
|
||||
monsters record those on the hero's map; monsters revert to 'unseen'
|
||||
boolean options can optionally have the form "name:value" with value taken
|
||||
from among "true", "yes", "on", or "false", "no", "off"
|
||||
|
||||
|
||||
Platform- and/or Interface-Specific New Features
|
||||
|
||||
Reference in New Issue
Block a user