Yeah, it maybe wasn’t engineered this way, but we end up with a shell script
hidden in the source tree, depending on m4 you wouldn’t run at runtime. A
system subtle enough to run tests against the Pike binary you just compiled
instead of the installed one. A marvel for a Pike core hacker :)
Well, mktestsuite is just a shell script that runs m4. There isn’t anything
that’s particularly “compile-time centric about it”. And certainly test_pike
could be modified to automatically update the test suite file if needed.
The m4 dependency means that you wouldn’t necessarily be guaranteed
Hello,
>> As a side note, maybe the brew Pike formula could be enhanced to
>> provide mktestsuite in the PATH ?
>
> I'm not sure what the best solution is for this; "mktestsuite" is kind of a
> generic name. Maybe we could add an option to test_pike to generate the
> testsuite?
Getting back
As a side note, maybe the brew Pike formula could be enhanced to
provide mktestsuite in the PATH ?
I'm not sure what the best solution is for this; "mktestsuite" is kind
of a generic name. Maybe we could add an option to test_pike to generate
the testsuite?
If some kind of interest,
> pike -x test_pike is a bundled tool for running testsuites (aka unit tests).
> I’m pretty sure the test_pike.pike script described in the link is
> essentially the same thing. I use it primarily in my standalone modules[1],
> but it certainly isn’t limited to that. I think you also need to
