The current output related option(s):

+-i   input_file_name
+-hi  include_header
+-ini include_ini
       pre_scene_command
       pre_scene_return
       post_scene_command
       post_scene_return


become(s):


+-sf_   scene_filename     string value only
+-sh_   scene_header       string value only
+-si_   scene_ini          string value only
+-ssi   scene_stdin        on|off             NEW
+-sn_   scene_name         string value only  NEW
+-sprc_ scene_pre_command  string value only
+-sprr_ scene_pre_return   string value only
+-spoc_ scene_post_command string value only
+-spor_ scene_post_return  string value only

Parsing code mostly there.

The stdin in option is a feature which has been requested over the 
years. I'll need to learn how other programs do this well. (I'll be 
thinking too about whether something similar might replace problematic 
parse_string hack).

We are often using the MS ini file editor syntax highlighting (without 
extra user set up Linux / Unix VIM users get the wrong syntax support 
too). Our .ini file format is similar, but not a strict match for it. I 
plan to start with much more restrictive .ini file support with the 
options changes above.

- No section support. Long ago, with much more restrictive file systems, 
there was a reason for this trick.

- All the .ini file inclusions will require using an ini option of flag. 
The yuqk fork has already implemented much of this change.

- No recursive inclusion (there was a thread some months back which 
touched on this being allow to some overall depth limit today). Also 
toying with not allowing ini files to include other ini files, but we'll 
see. It would make users ini option issues easier to debug/sort.

Bill P.

Post a reply to this message