Leon Timmermans

This can be fixed by using a `*$` prototype, and resolving it using `Symbol::quality_to_ref`

Generally speaking, I would recommend asking the maintainer before doing something as invasive like this. This contains two different changes. One is reorganizing the code: moving the header files to...

> https://metacpan.org/pod/Net::LDAP has the correct link That isn't very helpful when both the [search engine](https://metacpan.org/search?q=Net+LDAP) and the [distribution overview](https://metacpan.org/release/perl-ldap) link to the [pod](https://metacpan.org/pod/distribution/perl-ldap/lib/Net/LDAP.pod).

TAP has historically supported unnumbered test, so if you'd really want to go there, that seems like a more obvious route. That said, I don't think this really solves any...

We really want to have this. I'm not fond of the current mechanism, but given it's out there and there's a lot of stuff outputting it already it may be...

> I believe most libraries would support a failure just fine for both of those, its simpler that requiring an update to the libraries and forces stricter reasoning of tests...

> We should not be afraid to break old implementations and if anything that should be the correct behaviour. Old implementations should not ever ignore sub tests. This is a...

> Older parsers may or may not be able to cope with invalid subtests. The following will not fail with some of the parsers I have seen: Even as OKs...

> Allow for sub test numbering 1.1.1 and 1 I'm not sure what you mean with that exactly.

> Cause a parse error (Getting the consumer to upgrade their consumer) This is not acceptable at all. Specially not in situations where the producer and the consumer are distributed...