João Valverde 070aeddf76 Lift restriction on upper case protocol display filter names ... Unlike other header fields in filter expressions protocol names cannot contain upper-case letters. Remove that restriction. This should make start-up slightly faster as it remove an extra loop for each protocol filter name. This was added in 9ead15a6eb but I don't see a reason to have different rules for protocols and fields, it seems the README.developer was just being vague and conflating PROTOABBREV with PROTOFILTERNAME. The recommendation for lower case is a style recommendation, and it's a good one, but it should be applied uniformly. As long as we are not enforcing this for all field filter values there is no point in enforcing it just for protocol names and actually it is detrimental, e.g: hi2operations HI2Operations.IRIsContent HI2Operations.UUS1_Content_element HI2Operations.iRIContent HI2Operations.iRISequence HI2Operations.IRIContent HI2Operations.iRI_Begin_record_element HI2Operations.iRI_End_record_element HI2Operations.iRI_Continue_record_element HI2Operations.iRI_Report_record_element (...) It's weird and unexpected to have this difference and there is no technical reason to require it. What we should probably do is not include the protocol name in the FIELDFILTERNAME and have the registration mechanism append it to the PROTOFILTERNAME. Also disallow leading '-' everywhere in filter names, not just protocol filter names. It's a universal requirement.		2021-11-02 08:35:24 +00:00
..
CMakeLists.txt	…
EN301040.asn	…
HI2Operations.cnf	asn2wrs: Rename duplicated filter names	2020-12-15 10:54:58 +00:00
HI2Operations_ver11.asn	…
HI3CCLinkData.asn	…
PCESP.asn	…
TS101909201.asn	…
UmtsHI2Operations.asn	…
packet-HI2Operations-template.c	Lift restriction on upper case protocol display filter names	2021-11-02 08:35:24 +00:00