Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.lang.misc Subject: Re: A good subset of C Date: Sun, 25 May 2014 12:53:33 +1200 Lines: 24 Message-ID: References: <1jy1ogca55286$.hxrf634zi430$.dlg@40tude.net> <127sttidjvix.13z7pcgnrk5ay.dlg@40tude.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net Pk39ZHudkV4C1Z8fuk6gGQDrXycqdkufX5ZSdfw7x4ZeEX9L8A Cancel-Lock: sha1:y4/h5hYVyzQlV18t/6mYy8PvNTI= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:17.0) Gecko/17.0 Thunderbird/17.0 In-Reply-To: Xref: csiph.com comp.lang.misc:2270 Rod Pemberton wrote: > On Sat, 24 May 2014 19:04:54 -0400, Ian Collins > wrote: >> Rod Pemberton wrote: > >>> It hid information no more than C hides information. I don't exactly >>> "see" how information is "hidden" in C. Perhaps, I'm expecting an >>> explicit mechanism where there is none? So, maybe, I'm not grasping >>> where the hiding is occurring? ... >> >> The simple example of C's file I/O is a good example of information >> hiding. Do you know or even care what a FILE object is? >> > > Yes and no. > > No, I generally don't care. The 'struct' based FILE works just as well > 99.99% of the time. So you agree that C file I/O uses information hiding and that you grasp where the hiding is occurring? -- Ian Collins