Re-naming the package...?

[asgrim]

I've noticed when explaining what the tool does, folks jump to conclusion that this is used for comparing HTTP/REST API versions. I wonder if renaming the package could alleviate this problem. Would be better to do it before we tag anything as naturally it's (ironically) a big BC break ;)

Not sure WHAT to suggest though for naming, feedback welcome on this.

[asgrim]

• Roave\ABCD (A BC Detector)
• Roave\BCBC (BC Break Checker)
• Roave\BCBreakDetector

[Majkl578]

SignatureComparer?
SignatureComparator?
SignatureComplianceChecker? (inspired by C/C++ abi-compliance-checker)

[gnumoksha]

Application Interface Comparator.

[Ocramius]

I would probably specialise the package to just deal with BC Breaks and keep the naming in that scope, so roave/backwards-compatibility-check or such.

[ntzm]

backward-compatibility-checker is my vote

[Majkl578]

Since this is not a checker (as it returns non-zero code for BC issues), it should rather be backward-compatibility-enforcer.

[ntzm]

How about this-package-returns-a-non-zero-exit-code-if-your-code-is-not-backwards-compatible?