# from David Golden via RT
# on Sunday 23 August 2009 20:41:
>* In have_c_compiler, cache the results in the stash, not the
>properties, because it isn't actually a property, but we do want it to
>persist per session
I'm not sure what you mean by "per session", but $self->{stash} is not
persisted in _build/. So, it might not be a 'property', but
have_c_compiler() should somehow be cached by write_config() because
EU::CB's have_compiler() is an expensive operation of attempting to
compile a small c program. Thus, if it was true at configure time, we
don't want to repeat that effort at build time.
I'm guessing that "just stick it in properties" was the easiest way to
make this work when it was written. If there is some sort of "internal
use only" equivalent of properties, I'm not seeing it. Do we need to
add one?
I'm inclined to just call it a {_have_c_compiler} or even leave it as a
{have_c_compiler} property.
--Eric
