----- Original Message -----
From: "Sisyphus"
For the purposes of InlineX::CPP2XS (and perhaps other purposes, too), it
would make things easier if it did:
#################################
$o->{ILSM}{AUTO_INCLUDE} ||= $flavor_defs . $auto_include;
#################################
But I don't know whether that fixes a bug in validate(), or creates one,
or does neither.
As regards the tests in the I::CPP test suite it seems we can do it either
way, and it makes no difference.
In case you haven't spotted the relevance, validate() will currently
always prepend auto_include with $flavor_defs. But you can avoid that if
you use the latter.
And, for portability, we don't want the contents of $flavor_defs to appear
anywhere in the shipped C++ source code - hence the relevance to
InlineX::CPP2XS.
(Btw, don't stress about this .... I already have "workarounds" in place,
anyway :-)
Stress even less ... the original workaround was rather kludgy, but I've
found I can turn this into a non-issue by overriding
$Inline::CPP::Config::cpp_flavor_defs.
As long as you don't make $Inline::CPP::Config::cpp_flavor_defs readonly,
all should be sweet :-)
Cheers,
Rob
