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: 109fba,d95b511473b3a931 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,d95b511473b3a931 X-Google-Attributes: gid103376,public X-Google-Thread: 1014db,d95b511473b3a931 X-Google-Attributes: gid1014db,public From: "N. L. Sizemore" Subject: Re: Language Choice and Coding style Date: 1996/07/06 Message-ID: <31DEF0FC.4FDC@theriver.com>#1/1 X-Deja-AN: 164078408 references: <4re0la$qk6@news.ld.centuryinter.net> content-type: text/plain; charset=us-ascii organization: The River mime-version: 1.0 newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++ x-mailer: Mozilla 2.02 (Win16; I) Date: 1996-07-06T00:00:00+00:00 List-Id: steidl@centuryinter.net wrote (at end of very cogent argument): > > Can someone come up with a case where: > 1. hungarian notation is needed for variables > 2. (1) is not solved by some other common good coding style method > 3. the case is not ultra-specific (i.e. it justifies hungarian > notation as being a general good coding style method) > > -Jeff > > BTW, I tend to declare things in alphabetical order for just this > reason - to keep it down to a glance instead of an O(N) search. As a possible example meeting the stated desiderata I would offer certain types of transaction processing code. Assume: - A three-tier c/s architecture - Control under a transaction monitor/manager - A complex retrieval, i.e. , a data structure involving joins from several disparate data sources - a (potentially) heavy transaction workload - Coding for transaction logic (aka 'business rules') at the 2nd tier, i.e., the transaction server/router Under these assumptions reasonable code style requirements might include: - use local copies of data elements prior to 'prepare to commit' - avoidance of other than absolutely necessary context shifts, e.g., call/returns, RPCs, etc. - in line documentation of data types and/or sources which are defined externally An admittedly constrained example but not, I think, infeasible. -- ------------------------------------------------------------ || Come ride The River ------- http://www.theriver.com/ || ------------------------------------------------------------