Talk:Coupling (computer programming)

message: "...the gains in the software development process are greater than the value of the running performance gain."
I feel that this statement may be more opinionated than factual. Perhaps omission of this would be prudent?
:I agree, and I've reworded this to make it clear that this is merely an opinion. Lunalot 21:44, 19 January 2007 (UTC)
thread_title:  gains in the software development process 

message: I have just merged the contents of the article "Low-Coupling / High-Cohesion pattern" into this article here under a new section with the same name. "Low-Coupling / High-Cohesion pattern" is now a redirect to here (see also Merging and moving pages). — Adrian | Talk 20:40, 10 November 2005 (UTC)
thread_title:  Merge from the article "Low-Coupling / High-Cohesion pattern" 

message: You are in Dependency Hell when you want connect to the Internet, try to install a package to stablish the access and the package has a lot of dependencies. You cannot download the packages because you are not connected and you cannot connect because you cannot dowload the packages.--Mac (talk) 16:58, 5 February 2008 (UTC)
thread_title:  Dependency hell 

message: Can anyone include information about what are explicit and implicit dependencies ? And recursive implicit dependencies ?. --Nopetro (talk) 09:31, 11 February 2008 (UTC)
thread_title:  Explicit and implicit dependencies  

message: The concepts of coupling and cohesion were invented by Larry Constantine, not Glenford Myers. Myers was a student of Constantine's at IBM's Systems Research Institute. Although Myers book was published before Yourdon and Constantine's classic, primary sources (e.g., 1974 IBM SYSTEMS J. aricle) make clear the source of the core ideas.
Stirrer (talk) 17:14, 21 May 2008 (UTC)
thread_title:  Attribution 

message: The Fenton Metric is missing.
--phil (talk) 15:02, 21 June 2008 (UTC)
thread_title:  Where is the Fenton Metric? 

message: The is some unfortunate inconsistency in the terminology used to describe different types of coupling that makes an already challenging subject even more difficult to follow. In the "Types of Coupling" section seven different types are discussed, and in the "Module Coupling" Section four types are mentioned. Unfortunately two of these latter four (global and environmental) are not described in the earlier section. I'm not being pedantic, just trying to understand some difficult concepts. Presumably there are alternative names in use here but this in not made clear anywhere.
Inspeximus (talk) 07:15, 2 August 2011 (UTC)
thread_title:  Inconsistent Terminology 

message: Some programs aren't packaged and require specific compilers, or are packaged and require compiling of OTA updates. 
:104.176.16.56 (talk) 00:48, 27 April 2018 (UTC)
thread_title:  Compiler as a Dependency 

message: This section seems to have nothing to do with coupling, and indeed the relationship between performance and coupling was much clearer before this section was introduced. The clarity of the section itself has deteriorated over time.
KeithC (talk) 13:51, 10 August 2018 (UTC)
thread_title:  Performance issues 

message: The book name in the text of the article referenced in footnote 4 is not correct. The footnote is correct, the text reference lists the author, instead of the name of the book. Please fix. Gclose11 (talk) 21:55, 1 March 2023 (UTC)
thread_title:  The book name in reference [4] is incorrect. 

message: There is no mention of important types of coupling such as design-time versus runtime coupling, (execution) location coupling, creation coupling, call coupling, temporal coupling, data structure/data format coupling, inheritance coupling... 62.167.164.120 (talk) 14:54, 8 May 2023 (UTC)
thread_title:  This list of modes/types of coupling is extremely outdated