NFD » ndn-cxx

https://gerrit.named-data.net/4627 patchset 1 has the implementation of name::Component type and fixes for existing test cases, but there isn't any new test case yet. Please review API.

A design decision: in Component constructors, I'm putting TLV-TYPE parameter before TLV-VALUE, instead of adding it at the end with a default argument value. The reason is that TLV-TYPE comes before TLV-VALUE in "T-L-V".

https://gerrit.named-data.net/4627 has the test cases.

Upcoming commits:

• change all tlv::NameComponent to tlv::GenericNameComponent
• add some methods to append typed components in Name class

https://gerrit.named-data.net/4642 allows typed component in FinalBlockId element. I notice that the protocol does not forbid a zero-length GenericNameComponent to be FinalBlockId, but the existing API does not support that. Therefore, I'm introducing MetaInfo::getFinalBlock that returns optional<name::Component>, and deprecating the existing API.
The protocol envisions "Name component with TLV-TYPE 0 (zero) is reserved to indicate an invalid name component". However, I'm unable to implement as such, because legacy code expects a default-constructed name::Component to be a zero-length GenericNameComponent.

https://gerrit.named-data.net/4643 extends Name::append for typed component.
Existing Name::append(const Block&) encapsulates non-0x08 element into GenericNameComponent, and this behavior is preserved.

https://gerrit.named-data.net/4644 renames tlv::NameComponent to tlv::GenericNameComponent in files not touched by the above two changes.

During Name class changes, I notice a problem with getSuccessor algorithm. It is separated to #4570 to be triaged later.