>George: please go on at greater length (difficult, but it's a good cause).
>Functional cohesion? Which functions are coheding?
>The programs may be doing similar things?

Larry,

Without going into a tremendous amount of great detail, I'll try to sum this up rather simply. Functional cohesion refers to what a method/procedure/function does. The goal being one, and only one, thing. Doing something based on what called it is less cohesive, therefore, than doing a task or returning a value without regard to the caller. This, in and of itself, tends to make the method/procedure/function less re-usable than it might be otherwise. It also tends to cloud the issue of maintenance since you cannot tell what the module is supposed to do without knowing the caller at design time.

That work for you?

>Like, if this won't tell me who's calling, ¿como no?
>
>"What's that spell?"
>
>-Larry
>
>ps. (for the youth in chronological age) - FISH)

:-)