Ethereal-dev: Re: [Ethereal-dev] plugins version-subdirectory: Why?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Ulf Lamping" <ulf.lamping@xxxxxx>
Date: Wed, 16 Mar 2005 17:26:40 +0100
Ethereal development <ethereal-dev@xxxxxxxxxxxx> schrieb am 16.03.05 11:25:12:
> 
> Lars Ruoff schrieb:
> > 
> Good idea.
> How about using additionally a perl script, to scan for changes in the 
> plugin api. If it detects changes, it should exit with an error. Then we 
> make the buildbot run this perl script reporting any errors.
> 
> We have a list of exported symbols in libethereal.def. We would have to 
> look for the declarations of these symbols in all header files in /epan 
> and subdirectories.
> Then we compare the actual declarations with a declarations in a 
> reference file, which is just an older output of this script.
> If a difference is detected, the script output suggests to update the 
> reference file and the "plugin api version number" in the svn tree and 
> exits with an error.

Hmm, that won't help a lot, as the problem of an "always changing" API won't be solved by this either. Having a new plugin API version for each new Ethereal release won't be much helpful.

We would need a way to detect if the specific parts of the API used by that plugin changed or not since the time the plugin was generated.

Unfortunately, I don't see any way of using a script to detect this. A script could detect changes in the functions and parameters, but how should it detect semantic changes in these parameters, e.g. changing of an enum value used?

> 
> BTW, as already suggested by Ulf, it is time to retire the old api. If 
> time permits, I'd like to do the final changes this evening.
> 
That would be really nice!

Regards, ULFL

______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193