Do not use the module Config in B::C

[toddr]

Instead of using Config and bloating compiled code, Simply use the generated
B::C::Flags file to store %Config values. Then do a dirty import in B::C so the
code in B::C does not have to be altered.

This should solve a class of problems related to compiling in Config into
binaries that never use Config.

[atoomic]

++ for this commit

[rurban]

Smokes are green, but I don't like the bloat in B::C::Flags. we need only 21 from 1222 keys.
It makes more sense to keep this Flags file readable and maintainable. People need to be able to modify and maintain it.

$ perl -nle'/Config\{(.*?)\}/ and print $1' lib/B/C.pm | sort -u
archname
cc
ccflags
d_c99_variadic_macros
d_longdbl
dlext
i_dlfcn
ivdformat
ivsize
longsize
mad
nvgformat
ptrsize
static_ext
usecperl
usedl
useithreads
uselongdouble
usemultiplicity
usemymalloc
uvuformat

[toddr]

And when you add key 15, what happens when you forget to update Makefile.PL to be sure it's listed there?

[toddr]

B::C::Flags should be excluded from the binary so I see no reason why the bloat would be any different?

[rurban]

When a key is added, you'll get an empty value, yes.

[rurban]

Waiting for branch no_Config with f1cd880

[rurban]

f1cd880 broke it, investigating.

missed the d_dlopen key. made it now a restricted hash to error when missing a key with eab6e43

[rurban]

Merged 3 commits with eab6e43