Subject | RE: [IB-Architect] UDF Functions |
---|---|
Author | Leyne, Sean |
Post date | 2000-11-17T15:37:41Z |
Ann,
(After a very busy couple of weeks...)
So I've had a quick look at the definition of the AVG function, so
instead of 20 source code references where down to about 10 (if memory
serves). Most of the references are in syntax parsers (there is, of
course, more than 1).
What I found interesting is that I didn't actually see where the
implementation of AVG is actually coded.
Can you give me a pointer for this.
Sean
-----Original Message-----
From: Leyne, Sean [mailto:InterbaseArchitecture@...]
Sent: Wednesday, November 08, 2000 7:33 PM
To: 'IB-Architect@egroups.com'
Subject: RE: [IB-Architect] UDF Functions
Ann,
The 20 source code references, where for the new built-in function
EXTRACT! Sorry I should have mentioned the name ;-(
I would have expected the same to be true of any new function added to
the engine. Extract should be appropriate guidepost, since I viewed it
as a fair representation of most UDF functions - a keyword which accepts
values and returns a result.
I will also have a look at the implementation of AVG, thanks for the
pointer.
Sean
-----Original Message-----
From: Ann Harrison [mailto:harrison@...]
Sent: Wednesday, November 08, 2000 4:07 PM
To: IB-Architect@egroups.com
Subject: RE: [IB-Architect] UDF Functions
UDF mechanism to define built-in functions. The Novell thing
was pretty much a cheap way to get some additional capabilities
to that platform.
Look at the implementation of avg, and imagine something like
a blr_internal_function operator that took a list of blr_function_x
arguments that identified the function.
Regards,
Ann
To unsubscribe from this group, send an email to:
IB-Architect-unsubscribe@onelist.com
(After a very busy couple of weeks...)
So I've had a quick look at the definition of the AVG function, so
instead of 20 source code references where down to about 10 (if memory
serves). Most of the references are in syntax parsers (there is, of
course, more than 1).
What I found interesting is that I didn't actually see where the
implementation of AVG is actually coded.
Can you give me a pointer for this.
Sean
-----Original Message-----
From: Leyne, Sean [mailto:InterbaseArchitecture@...]
Sent: Wednesday, November 08, 2000 7:33 PM
To: 'IB-Architect@egroups.com'
Subject: RE: [IB-Architect] UDF Functions
Ann,
The 20 source code references, where for the new built-in function
EXTRACT! Sorry I should have mentioned the name ;-(
I would have expected the same to be true of any new function added to
the engine. Extract should be appropriate guidepost, since I viewed it
as a fair representation of most UDF functions - a keyword which accepts
values and returns a result.
I will also have a look at the implementation of AVG, thanks for the
pointer.
Sean
-----Original Message-----
From: Ann Harrison [mailto:harrison@...]
Sent: Wednesday, November 08, 2000 4:07 PM
To: IB-Architect@egroups.com
Subject: RE: [IB-Architect] UDF Functions
>not
>From: Dalton Calford [mailto:dcalford@...]
>
>3.) Is there a reason why the common udf's (or a subset of them) can
>become part of the new version?At 03:31 PM 11/8/2000 -0500, Leyne, Sean wrote:
>I have done some research on this subject, the lack of built-inUmmm maybe that's why the intention was not to use the existing
>functions has been a pet peeve of mine since I started using IB.
>
>Aside from the fact, that it appears that the definition and
>implementation of the functions is spread across some 20 source code
>files, there is no reason why this can't be done.
UDF mechanism to define built-in functions. The Novell thing
was pretty much a cheap way to get some additional capabilities
to that platform.
Look at the implementation of avg, and imagine something like
a blr_internal_function operator that took a list of blr_function_x
arguments that identified the function.
Regards,
Ann
To unsubscribe from this group, send an email to:
IB-Architect-unsubscribe@onelist.com