Lionel, People tend to use the term modularity in one of two ways.
>> 1) a function (or procedure, subroutine, etc) is a module, >This is taking a part as the whole, but I never eard about such a confusion. Don't forget that the term module has been around since the earliest days of computing. In many languages a function (or procedure etc) is the only construct that might be considered a standalone entity. These days languages that have a higher level packaging construct are more common and therefore some developers use the term to refer to instances of such a construct. I find it is necessary to read papers very carefully to find out what definition of module the authors are using. Metrics people in particular often use function <-> module. >The most common confusion is between class and module, maybe because most programming >language don't differenciate them. This problem is relatively new (well since the 90's). ---------------------------------------------------------------------- PPIG Discuss List ([EMAIL PROTECTED]) Discuss admin: http://limitlessmail.net/mailman/listinfo/discuss Announce admin: http://limitlessmail.net/mailman/listinfo/announce PPIG Discuss archive: http://www.mail-archive.com/discuss%40ppig.org/
