Refactor config - split read_config into read_config and resolve_config
authorRichard Levitte <levitte@openssl.org>
Mon, 18 May 2015 00:57:24 +0000 (02:57 +0200)
committerRichard Levitte <levitte@openssl.org>
Wed, 20 Jan 2016 21:07:59 +0000 (22:07 +0100)
commitbd5192b1013b68373c47bdca8d68229906171695
tree1771afa9878e8bcd17baf08b307bb7f9d018cd1a
parentbb56561adbb6d2728b05e2df08c0575c38a46249
Refactor config - split read_config into read_config and resolve_config

Split the read_config function into read_config that ONLY reads the
configuration files but doesn't try to resolve any of the
inheritances, and resolve_config which resolves the inheritance chain
of a given target.  Move them to the bottom of Configure, with the
rest of the helpers.

Have a new small hash table, %target, which will hold the values for
the target the user requested.  This also means that all access to the
current target data can be reduced from '$table{$target}->{key}' to a
mere '$target{key}'.

While we're at it, the old string formatted configurations are getting
obsolete, so they may as well get deprecated entirely.

Reviewed-by: Rich Salz <rsalz@openssl.org>
Configure