Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!mcsun!ukc!edcastle!aipdc From: aipdc@castle.ed.ac.uk (Paul Crowley) Newsgroups: comp.object Subject: Re: C++ and waitresses Message-ID: <10549@castle.ed.ac.uk> Date: 25 May 91 20:03:19 GMT References: <2325@media03.UUCP> <1991May24.175143.17793@kestrel.edu> Organization: Put your analyst on danger money, baby! Lines: 27 In article purtill@morley.rutgers.edu (Mark Purtill) writes: >gyro@kestrel.edu (Scott Layson Burson) writes: >>I think one answer is that there should be a definitive style guide >>for C++, one which is comprehensive enough that it comes to be >>considered as essential a desk reference as the reference manual >>itself. Does anyone know if someone is writing such a book? Perhaps >>I should. > You could write one, but I doubt that it would be >"definitive". People can't even agree on how to *indent* C; do you >really expect them to agree on how to *use* C++? I think some sort of C++ style guide would be a good idea. Plenty of companies have _rules_ (not guidelines) on how to indent your programs, what names to give your procedures and variables, and so on. C++ offers potential for obfuscation that leaves C standing, and some sort of guidebook would not only help others read your programs (in some cases _allow_ others to read your programs) but also help you program large things since if you know you did 99% of it in the suggested style, you can hold the program in your head more easily and you know the object you designed last year doesn't do weird things. I'd especially appreciate advice on where to put your pointers. And I've already thought of the joke about this and my signature. ____ \/ o\ Paul Crowley aipdc@castle.ed.ac.uk \ / /\__/ Part straight. Part gay. All queer. \/