Subject | Re: [Firebird-Architect] UDR Engine |
---|---|
Author | Alex Peshkov |
Post date | 2008-06-25T07:39:38Z |
On Tuesday 24 June 2008 17:35, Adriano dos Santos Fernandes wrote:
DDL level. But may be it's really better to call it BINARY? In order not to
confuse people. Certainly, everyone who wants can add any entries to his
config file. But in default configuration I prefer not to have confusing
entries - they may become a source of multiple questions in support :)
> Alex Peshkov escreveu:Thank you, understood - this is in order to provide language information to
> > On Tuesday 24 June 2008 17:02, Adriano dos Santos Fernandes wrote:
> >> <language CPP>
> >> plugin_module UDR_engine
> >> </language>
> >>
> >> <language DELPHI>
> >> plugin_module UDR_engine
> >> </language>
> >
> > Adriano, when I see a need to specify in config file what compiler was
> > used to create binaries, I stop to understand anything. What if someone
> > wants to write plugin using bcc32 - borland C compiler? Should it be
> > Delphi or C++? What to do if assembler is used? Or fortran-77?
> > This is compiled binary, no need to add any more language information.
>
> I do have only two alternatives:
> 1) Call "NATIVE" or "BINARY", the language implemented by this plugin
> 2) Change LANGUAGE DDL clause to PLUGIN - it doesn't invalidated the
> proposed UDR plugin
DDL level. But may be it's really better to call it BINARY? In order not to
confuse people. Certainly, everyone who wants can add any entries to his
config file. But in default configuration I prefer not to have confusing
entries - they may become a source of multiple questions in support :)