Thanks - I obviously didn't look well enough. That solves that problem... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Guy Harris Sent: 12 February 2007 17:35 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Controlling Tshark output format
Douglas Pratley wrote: > b) I didn't want to restrict the possible names of fields. So far, all > the ones in Wireshark are "sensible" strings, but I can't find any code > that restricts them, so they might contain commas, spaces, etc. See the loop in proto_register_field_init() which scans hfinfo->abbrev to make sure it only contains alphanumerics, "-", "_", and ".". _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies within the Detica Group plc group of companies. Detica Limited is registered in England under No: 1337451. Registered offices: Surrey Research Park, Guildford, Surrey, GU2 7YP, England. _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
