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.1 required=5.0 tests=BAYES_05,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f8c65,30e368bdb3310fe5 X-Google-Attributes: gidf8c65,public X-Google-Thread: fac41,af40e09e753872c X-Google-Attributes: gidfac41,public X-Google-Thread: 109fba,f292779560fb8442 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,30e368bdb3310fe5 X-Google-Attributes: gid103376,public X-Google-Thread: 1008e3,30e368bdb3310fe5 X-Google-Attributes: gid1008e3,public X-Google-Thread: 10db24,30e368bdb3310fe5 X-Google-Attributes: gid10db24,public X-Google-Thread: 1014db,30e368bdb3310fe5 X-Google-Attributes: gid1014db,public From: garyl@enter.net (Train) Subject: Re: Hungarian notation Date: 1996/05/23 Message-ID: <4o1ilm$1b0@news.enter.net>#1/1 X-Deja-AN: 156293151 references: <4adem2$b5s@mercury.IntNet.net> <4n6off$6e2@mikasa.iol.it> <3198F30F.2A2@zurich.ibm.com> <4nsg3f$liu@solutions.solon.com> <31a3b322.442404233@sqarc> <4o19k3$o4b@goanna.cs.rmit.EDU.AU> organization: ENTER.NET mime-version: 1.0 newsgroups: comp.lang.ada,comp.lang.c++,comp.lang.c,comp.lang.modula3,comp.lang.modula2,comp.edu,comp.lang.eiffel Date: 1996-05-23T00:00:00+00:00 List-Id: In article <4o19k3$o4b@goanna.cs.rmit.EDU.AU>, ok@goanna.cs.rmit.EDU.AU says... hI rarely comment, but .... I have been teaching for over 30 years and programming since 1960. During that time I've seen a lot of code an d blessed/cursed others depending on how easy it was to understand the code. The Micro$loth conventions have made it extremely difficult to pick up a snippet of code and understand what's going on -- unless you are part of that team (maybe 1000 programmers?). How else would they coordinate? At IBM in the early '60s we had the same problem and "rules" were develeped to handle it. One I remember was that 75% of all code must have comments. This lead to lines of code saying ST R4,7 (figure it out) with a comment of "Store 7 in register 4." As you can imagine, 75% comments didn't help a great deal. I've seen all kinds of standards and been part of writing horrible ones myself that dictate where indentation will be, how structures are to be used, etc. but the end result is: if the coder intends to be clear and communicate it really doesn't matter what standards he/she uses, the code will be clear. My students (college and commercially) always start out coding away before any design, no comments, and no outlining structure. As they have problems I gently (usually) point out that I can't find the end of a Select (Switch, or whatever) because they don't line up, I make changes to make life easier and help them. You don't really have to tell folks not to spill hot coffee all over themselves --- they do it once and then they start avoiding it. I'd like to feel that whatever sloppy code you give me I can figure it out, but I am getting old and tired and less likely to take the time and comment the mental energy to plow through really bad layout, naming, useage, etc. So now I only help when I must or get paid to do it. There ... now I feel better.