![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||
|
What is the point of this article? Are circular dependencies acceptable or are they to be avoided ?(the article implies "unavoidable"). Do such dependencies only exist between two classes or can the cycles be larger (e.g., A->B->C->D->A) (the article implies "two"). Do such dependencies only exist in C++ or do they appear in other OO languages? (the article implies c++ is what's important). Yes it's "only" a stub. But without knowing what the intent of having the article is in the first place, it's hard to know how to complete it (or whether it is even worth bothering).
This article implies that there is a circular dependency between C++ and circular dependencies when in fact there are no dependencies between C++ and circular dependencies as all. Specifically the article seems to imply that C++ depends on circular dependencies and that circular dependencies depend on C++. I can assure you, however, that C++ does not depend on circular dependencies, and in fact, limited C++ code can be written with no dependencies at all or even with non-circular dependencies. Likewise, circular dependencies do not depend on C++, but can in fact, exist in programs written in other languages (as a PHP developer I can prove this).
Um. See [Recursion] —Preceding unsigned comment added by 210.15.222.106 ( talk) 01:45, 1 July 2008 (UTC)
This article could be generalized for circular dependencies in software design in general. Some thoughts:
A Circular Dependency in a software design is a mutual dependency between two modules which either directly or indirectly depend on each other to function properly.
Circular dependencies should be avoided if possible in software design because of their negative effects. Some of these effects are:
![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||
|
What is the point of this article? Are circular dependencies acceptable or are they to be avoided ?(the article implies "unavoidable"). Do such dependencies only exist between two classes or can the cycles be larger (e.g., A->B->C->D->A) (the article implies "two"). Do such dependencies only exist in C++ or do they appear in other OO languages? (the article implies c++ is what's important). Yes it's "only" a stub. But without knowing what the intent of having the article is in the first place, it's hard to know how to complete it (or whether it is even worth bothering).
This article implies that there is a circular dependency between C++ and circular dependencies when in fact there are no dependencies between C++ and circular dependencies as all. Specifically the article seems to imply that C++ depends on circular dependencies and that circular dependencies depend on C++. I can assure you, however, that C++ does not depend on circular dependencies, and in fact, limited C++ code can be written with no dependencies at all or even with non-circular dependencies. Likewise, circular dependencies do not depend on C++, but can in fact, exist in programs written in other languages (as a PHP developer I can prove this).
Um. See [Recursion] —Preceding unsigned comment added by 210.15.222.106 ( talk) 01:45, 1 July 2008 (UTC)
This article could be generalized for circular dependencies in software design in general. Some thoughts:
A Circular Dependency in a software design is a mutual dependency between two modules which either directly or indirectly depend on each other to function properly.
Circular dependencies should be avoided if possible in software design because of their negative effects. Some of these effects are: