Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 26377: /trunk/epan/dissectors//trunk/epan/dissectors/: ncp2222.py

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Stig Bjørlykke <stig.bjorlykke@xxxxxxxxx>
Date: Thu, 9 Oct 2008 00:45:29 +0200

On 8. okt.. 2008, at 15.14, Greg Morris wrote:

Well that white space was there on purpose...
{ 15, "Read Class Definition " },

Ups, I'm really sorry about that. But why do we need the space in this particular entry and not any of the others? Is the 15 entry the only one used in this way? And can't we add the space where we use the value, in packet-ncp2222.inc?

And, as Jaap, I would like a comment for this.


--
Stig Bjørlykke



  • References:
    • Re: [Wireshark-dev] [Wireshark-commits] rev 26377: /trunk/epan/dissectors//trunk/epan/dissectors/: ncp2222.py
      • From: Greg Morris
  • Prev by Date: [Wireshark-dev] dropped packets stats for dumpcap/tshark ring buffer mode
  • Next by Date: Re: [Wireshark-dev] [Wireshark-commits] rev 26376: /trunk/ /trunk/: manuf
  • Previous by thread: Re: [Wireshark-dev] [Wireshark-commits] rev 26377: /trunk/epan/dissectors//trunk/epan/dissectors/:
  • Next by thread: [Wireshark-dev] displaying TLV parameters - proto_tree_add_item_hidden for type no longer available, now have one line for type, one line for value
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation