Hi Jasper,

Do you have some literature with that use. I honestly have googled: 

and the first result I got 

It is kind of what I said:

"""The purpose is to shield from change all systems (or human users) on the 
other end of the interface. Confusingly, the term refers to overall 
*invisibility* of the component, it does not refer to *visibility of 
component's internals* (as in white box 
<https://en.wikipedia.org/wiki/White_box_(software_engineering)> or open 
system <https://en.wikipedia.org/wiki/Open_system_(computing)>)""""

On Saturday, August 31, 2019 at 10:53:26 AM UTC+2, Jesper Louis Andersen 
> On Thu, Aug 29, 2019 at 7:02 AM Leo Lara <l...@leopoldolara.com 
> <javascript:>> wrote:
>> Hi Michael,
>> The way I always have seen "transparent" used in software engineering is, 
>> that the user of something (lirabry, service, framework, etc) can use it 
>> without knowing its internal details, just normally, and the magic is done 
>> in the thing used.
> People use this in the opposite form at times. That is, a transparent data 
> structure is one where you know its internal representation (and can rely 
> on that in your part of the program). In contrast an opaque data structure 
> is abstractly encapsulated: even if you know its internals, you cannot get 
> at it. Thus the latter is the former and the former is the latter compared 
> to your use.

You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to