I guess the problem can be that if someone needs to restart a
server, this functions will not be loaded automaticaly and you can
have a lot of databases that use this functions. Applications will
not run properly until they are registered.

I suppose there is also some overhead caused by external calls than
might slow down the server as well. A lot of functions are very
commonly used, why not integrate them to the engine?, and still be
able to register other functions not commonly used as UDFs.

I would incorporate these funtion because they are very commonly
used:

Abs
Ceiling
Div
Floor
Lpad
Ltrim
Mod
Rpad
Rtrim
Strlen

And move the rest of the 'ib_udf' functions to a 'Trig_udf'
o 'Math_udf'.

Whath do you think about the Update and Delete syntax?

Cheers.



--- In Firebird-Architect@yahoogroups.com, "Claudio Valderrama C."
<cvalde@u...> wrote:

> Antonio Mejia wrote:
> >
> > I would also like to have all the UDFs incorporated like native
> > functions!.
>
> Can you explain what's the problem with the current configuration?

Is it too

> hard to use a shared library or DLL that comes with the

installation? Or the

> problem is that you don't want to do the UDF declarations in each

database?

> I don't see any advantage in putting ib_udf inside the engine.
>
> C.