id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
225	getenv() access (read-only) variables also from .INI files	Yuri Dario	bird	"The main problem with environment variables is that they need to be saved to config.sys to get proper setup, and this requires a reboot under os/2.

It will be nice if getenv() will try to read variable value also from a specialized INI file, so we can easily change values on the fly using regedit (or similar tools).

The INI file should be located into hardcoded location (e.g. %ETC%) and maybe into user home (overrides global ini).

INI should save data in the format: key=variable_name, value=type,value
Data can be stored also on a per-program setup, using key=program_name+variable_name; program specific setup has priority over global define.
value will store a string, it will be nice to add some macro expansion to allow extending config.sys variables.

Writing to INI values using setenv()/putenv() is not allowed.

INI values should be added at program enviroment pool at startup, so getenv() and friends will access them without changes to code. Also childs will inherit automatically the new environment.
"	enhancement	new	normal	libc-0.7	libc-backend	0.6.2	normal