# from Michael G Schwern
# on Saturday 21 March 2009 17:02:
>> Hmm, what if there were a module named 'compiler'? Not sure I want
>> to play that game through though.
>
>Having module wrappers confirming the existence of external utilities
> and an API/config to where they may be found and how they are run may
> be the simplest game to play. ExtUtils::CBuilder being one, and
> possibly the most complicated, example.
So that brings us back to where I started, which is that build_requires:
ExtUtils::CBuilder is at least a definitive "not pure_perl" indicator.
Except, Inline::C and swig are at least two other possible cases.
So, would pure_perl or some sort of arch_independent flag be warranted?
--Eric
--
"Left to themselves, things tend to go from bad to worse."
--Murphy's Corollary
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
