Le 16/11/2010 21:13, Helge Kruse a écrit :
> Am 16.11.2010 19:05, schrieb Stephen Fisher:
>> On Tue, Nov 16, 2010 at 06:37:32PM +0100, Helge Kruse wrote:
>>> Is it guaranteed that a 1.2.x plugin runs with Wireshark 1.4.x?
>> Jaap and Joerg are referring to the same stable branch, so any newer
>> version of 1.2.x than the one you compiled with (or newer 1.4.x than the
>> one you compiled it with).  This makes sense because only important bug
>> fixes are moved from the development back into the newer stable branches
>> and no new features.  I just didn't think we were verifying that bug
>> fixes never broke the ABI, although I can see why they never or at least
>> rarely would.
> Ok, I understand that life cycle. But I cannot convince anybody to
> update there 1.2.x installations to 1.4.x.
>
> So I must now decide if I have to provide a DLL compile with the 1.2.x
> header and libs and an additional DLL compiled with the 1.4.x header and
> libs. I don't think about the development branches (1.3.x).
Seems better.
I know at least 1 modification :
- stats_tree_register prototype changed
But it could have many other modifications which are not visible by the 
compiler.
On function prototype or struct definitions ...

> Sorry, if this additional question is annoying. But unfortunately I did
> not get the answer from your mail. I'm sure this would be my fault.
>
> Helge
>
> ___________________________________________________________________________
> 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
>
>


-- 
Wireshark Generic Dissector http://wsgd.free.fr

___________________________________________________________________________
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

Reply via email to