Matching strings return non-zero distances

[johnmarkpittman]

Using the default value for the matchWeight parameter, the affineGapDistance function returns len(string_a) as the distance between two strings that match exactly, and normalizedAffineGapDistance returns 0.5.

Is this intended behavior? I looked through the referenced paper, but did not see any discussion of this.