[vdr] Feature request: suggestion for cPlugin
cwieninger at gmx.de
Thu Aug 18 16:54:04 CEST 2005
----- Original Message -----
From: "Klaus Schmidinger" <Klaus.Schmidinger at cadsoft.de>
To: <vdr at linuxtv.org>
Sent: Thursday, August 18, 2005 4:42 PM
Subject: Re: [vdr] Feature request: suggestion for cPlugin
> The clean method is for the "server" to provide a proper public member
> function and for the "client" to include the plugin's header file.
> Determining whether or not a plugin is present doesn't change through
> that - you already do that now, don't you?
but the big disadvantage are the dependencies at compile time. If the user
wants interaction between plugins he would have to set any defines in the
makefile. Thats not the case if there is a general purpose interface.
You may be right concerning the semantics, but why explaining the semantics
only in a header file? If there's a general interface, the documentation of
the protocol could also be part of the readme (or a readme for developers).
More information about the vdr