Hi,
Well, go ahead and create such a page under /Development
Thanks,
Jaap
Send from my iPhone
On 4 feb 2010, at 18:01, Beth <[email protected]> wrote:
It seems I'm not the only one who got bitten by this change (several
times - I'm a slow learner).
Just wondering, is there a "troubleshooting" wiki somewhere that
collects this sort of knowledge? I'd love to see something
organized by the many mysterious compile or execution failure
messages, with likely trouble sources for each. So when you get the
inevitable "Runtime exception" popup with no further explanation, at
least you have someplace to look it up, with a list of possible
goofs to look for in your code.
And perhaps it would ease the frustration of the developers who
uncover these issues, knowing they have someplace to report it where
it will help others avoid the same difficulty.
On Thu, Feb 4, 2010 at 10:40 AM, Bill Meier <[email protected]>
wrote:
Change the BASE_HEX to BASE_NONE.
Non-numeric types (FT_STRING, FT_BYTES, etc) now require BASE_NONE.
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
