Yes, you need to trust that the person in charge of the inside is doing what you expect. Which sometimes you only find out if he tells you what he's doing, because he may not know or care what you expect.
Hi Don,Are we talking OOP and encapsulation here?Then you only should know what goes in and what comes out!regardsKeith.Am 07.02.2012 um 01:00 schrieb don kretz:Unless, of course, it is intended that you not know, and you should assumeit's a black box and what it does and how it does it isn't anything you shouldcount on in the future. Which is a legitimate approach; but it should bemade explicit._______________________________________________On Mon, Feb 6, 2012 at 3:57 PM, don kretz <dakretz@gmail.com> wrote:One shouldn't need to examine the source code to anyone's program tofind out what it does. Which could be something else entirely tomorrow.On Mon, Feb 6, 2012 at 3:53 PM, don kretz <dakretz@gmail.com> wrote:
Some of the Publish-On-Demand services recommend you do exactlythat. And their requirements are quite similar.On Mon, Feb 6, 2012 at 3:50 PM, Jim Adcock <jimad@msn.com> wrote:
>If I would follow your way of arguing things lets all just take one of theActually a better idea than most floated here.
most widely used formats on the planet docx!
_______________________________________________
gutvol-d mailing list
gutvol-d@lists.pglaf.org
http://lists.pglaf.org/mailman/listinfo/gutvol-d
gutvol-d mailing list
gutvol-d@lists.pglaf.org
http://lists.pglaf.org/mailman/listinfo/gutvol-d
_______________________________________________
gutvol-d mailing list
gutvol-d@lists.pglaf.org
http://lists.pglaf.org/mailman/listinfo/gutvol-d