From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,57f23cc4dd455d6c,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-01-12 01:39:11 PST Path: nntp.gmd.de!Germany.EU.net!EU.net!uknet!hrc63!gmrc.gecm.com!valiant!bill From: bill@valiant (R.A.L Williams) Newsgroups: comp.lang.ada Subject: C++ Envy Date: 12 Jan 1995 09:39:11 GMT Organization: GEC-Marconi Research Centre Message-ID: <3f2tbv$r5o@miranda.gmrc.gecm.com> NNTP-Posting-Host: valiant.gmrc.gecm.com X-Newsreader: TIN [version 1.2 PL1] Date: 1995-01-12T09:39:11+00:00 List-Id: Look chaps, this is getting a bit silly. Assume that I want to change the functionality of a piece of code that I've picked up from somewhere. Why should I bother with sma****se tricks like the ones that have been suggested? Why not dive in and hack the code! This technique also works in Ada83 and Ada95! The point about 'private' in C++ or Ada is that it is an indication to the user that part of the interface is NOT meant to be mucked about with. You, the user, still have to have sufficient self-discipline not to muck around with it. As an added bonus, the compiler will tell you if you do it by accident. That's what it's for -- to pick up mistakes! Bill Williams