|
>> Using faster hardware doesn't improve the process of coding. >>> > >sure it does. > result = ProcedureCall( input1: input2 ) ; > >is more readable than: > ProcedureCall( result: input1: input2 ) ; > >however, the 2nd version uses less CPW to execute. Historically, i5 >programmers have to choose the efficient, less readable method because >i5 CPW is many times the price of p5 CPW. The result is less readable >code. > >-Steve I have been called a "performance nut" and I wouldn't even consider #2 because of performance. If the result is something larger than 16 bytes I would consider using a pointer, if the result is larger than 32 bytes I wouldn't consider using anything other than a pointer. Duane Christen NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.