Re: Language Choice and Coding style

["N. L. Sizemore" <bolshev@theriver.com>]

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/ ||
------------------------------------------------------------