[lazarus] About compatibility???
nc-gaertnma at netcologne.de
Fri Mar 8 03:21:06 EST 2002
On Sat, 09 Mar 2002 02:53:37 +0100
Matjaz Mihelic <matooo at email.si> wrote:
> Basically, idea goes like this
> instead of TDataLink for TDBEdit
> Add a wrapper to TControl, TEdit has inherited that and our new TEdit
> can be controled from anywhere or any data structure same as TLabel,
> TListbox.... >>>> Our wrapper would mean same control over value and
> state of any kind of control.
> This way using my suggestion there would be a wrapped control over
> editing, but easy gaining compatibility with Borland.
> Hasn't nobody else but me being bored using one control set for accesing
> normal input, one control set for DB, one control set to control for
> accesing Btrieve....???? I already tried to do something like that on
> Delphi, but the damn f...up was closed for any kind of internal lower
> editing of components. I would just end up deriving another set of
> components??? Bugger...
I like the idea.
> In case of preprocessor, I was asking about. Wouldn't be nicer to write
> a preprocessor that knows how to <#include somelibrary.h>, than waiting
> some of us to translate C headers in pascal (that's first idea that
> comes to my mind, and this one would put project much further than it
> really is, there would be no need to develop or translate things already
> done, but case of preprocessing I'm thinking one is simply as suggested
> >> IDE specified preprocessor tool, started in another CVS project
> completely out of, or with lazarus but different branch (This way
> lazarus wouldn't suffer any consequences, but gain a lot))?
Since it is impossible to translate any c header file to good pascal code, the current h2pas is the better solution.
I would like to add a h2pas frontend to the IDE, so that using c libraries will become much easier. But before that, h2pas must be improved.
More information about the Lazarus