Adriano dos Santos Fernandes wrote:

>
> DECLARE EXTERNAL FUNCTION <name>
> [ <parameter list> ]
> RETURNS <data type>
> ENTRY_POINT '<entry point>'
> LANGUAGE <language>
>
> ALTER EXTERNAL FUNCTION <name>
> [ ENTRY_POINT '<entry point>' ]
> [ LANGUAGE <language> ]
>
> [ Note: Objective of this branch was not fix legacy problems, but our
> functions is not well defined as the procedures are. For example,
> functions parameters doesn't have names. Instead of introduce CREATE
> FUNCTION syntax, I just extended the current syntax of UDFs statements.
> Since this work is target for V3, I think the general enhancements
> (parameter names, grants, owner) to functions should be done direct in
> HEAD.

Am I right in understanding that the suggested syntax is temporary and
should be replaced with a CREATE/ALTER/DROP FUNCTION in v3.0, while
legacy UDFs will still be using the DECLARE syntax? If so, I have no
objections. But, in this case your reply regarding EXTERNAL NAME becomes
weak as DECLARE EXTERNAL FUNCTION will still use the ENTRY_POINT keyword
while CREATE FUNCTION doesn't contain the EXTERNAL keyword.

> The files are all using int's to represent sizes, positions and whatever
> matters. Though I prefer int's, there is no problem if you all decides
> to using uint's.

Unsigned, please.

> When Firebird is initializing, it opens all *.conf files from
> <fbroot>/plugins.

I'd prefer a deferred plugins initialization.

More tomorrow :-)


Dmitry