Re: Procdures, triggers, alerters and rules

"Rebecca Riordan" <rebeccar_at_magna.com.au> wrote:

>Sean,
>
>Rather depends on your environment, designers have a distressing tendency to
>re-define these terms. Generally, though, a "procedure" is a bit of code
>that does something, but doesn't return a result. Sometimes "procedure" is
>used generically for any bit of code. Sometimes "function" is the generic
>term. Very irritating.

     A procedure might or might not return a value, but a function does return a value.

[snip]

Sincerely,

Gene Wirchenko

C Pronunciation Guide:

     y=x++;     "wye equals ex plus plus semicolon"
     x=x++;     "ex equals ex doublecross semicolon"