Talk:Information hiding

message: :In computer science, the principle of information hiding is the hiding of design decisions in a computer program that are most likely to change, thus protecting other parts of the program from change if the design decision is changed.
Aren't the decisions usually hidden implementation decisions rather than design decisions? - furrykef (Talk at me) 12:42, 6 Mar 2005 (UTC)
thread_title:  Design decisions 

message: I came to this article through the encapsulation disambiguation page. However, it seems that the very first reference to this term points back the same disambiguation page. What gives?? Folajimi(talk)
:Be bold!  I dunno.  I think I put it in, probably without looking.  Here, I'll be bold instead. --Mgreenbe 16:29, 26 January 2006 (UTC)
thread_title:  Encapsulation issue. 

message: In the History section, second paragraph, the word "Example," which begins the first sentence, seems out of place, but I am not sufficiently familiar with this topic to boldly delete it. Bustter (talk) 23:08, 19 January 2010 (UTC)
thread_title:  what is "Example Information hiding?" 

message: I think the Encapsulation (computer programming) page would be a better place for the section "Relation to object-oriented programming". Also, it doesn't seem to explain what it states in it's title. I will move the section until someone rejects this. Kaartic (talk) 16:06, 1 October 2016 (UTC)
thread_title:  Moving topic "Relation to object-oriented programming" to "Encapsulation" page 

message: Information-hiding, or data hiding, has traditionally been used for dual purposes of future-proofing (the same purpose as in implementation-hiding) and encapsulation (i.e. enforcement of invariants). This article's introduction only mentions the former. There is also a discussion on the talk page of encapsulation which promotes the conflation of data hiding and encapsulation. Encapsulation is distinct; the enforcement of invariants additionally employs exception safety (where applicable), synchronization, and a swathe of other programming constructs which are used to moderate the things that can occur both inside and outside privileged scopes. This page should present information hiding as a single, specific design construct which is used to express principles such as future-proofing and encapsulation, not as a principle in itself. 184.102.64.32 (talk) 07:52, 7 July 2020 (UTC)
thread_title:  Apparent conflation of implementation-hiding, information-hiding, and their applications. 

message: The term 'change'
 was used incorrectly, 
and connected to one action= limiting. 
Misdirection, 
rather than 
'hiding information' 
is a clearer message. 
Of course how does one explain how to think abstractively,  two times? And do you mean two abstract streams of thought, or thoughts, at the same time? or do you mean, two streams of abstractive thinking stacked, one on top of the other?
pstract'. It has no singular or plural, as it i, and it just spirals on and out and all around from there.  Do you realise thw implications of pretending to be cahleva, in these 'meaning levelling' times?times? 49.194.46.174 (talk) 07:22, 29 May 2024 (UTC)
thread_title:  Why is the change, confined to processes that follow change? 

message: Once the words 'more general' have been read, how can anyone read on? For anything to change its sliding scale of the sliding scale, one might slide,  right off the flipping scale? 49.194.46.174 (talk) 07:27, 29 May 2024 (UTC)
thread_title:  There is no logic