I found many wine sources use not a pointer,but a sequence . for example: krnl386.exe16/dma.c: for(i=0,p=(char*)DMA_CurrentBaseAddress[channel];i<ret*size;i++) msdaps/usrmarshal.c: for(prop = 0; prop < rgPropertySets[prop_set].cProperties; prop++) I know in some cases to use sequences are wiser way than pointers, but so many of them are used in loops. Should I change them?
On 8/30/2013 16:33, matyapiro31 wrote:
I found many wine sources use not a pointer,but a sequence . for example: krnl386.exe16/dma.c: for(i=0,p=(char*)DMA_CurrentBaseAddress[channel];i<ret*size;i++) msdaps/usrmarshal.c: for(prop = 0; prop < rgPropertySets[prop_set].cProperties; prop++) I know in some cases to use sequences are wiser way than pointers, but so many of them are used in loops.
I guess by sequences you mean arrays?
Should I change them?
Change them to what? And what will it solve?
On 08/30/2013 02:33 PM, matyapiro31 wrote:
I found many wine sources use not a pointer,but a sequence . for example: krnl386.exe16/dma.c: for(i=0,p=(char*)DMA_CurrentBaseAddress[channel];i<ret*size;i++) msdaps/usrmarshal.c: for(prop = 0; prop < rgPropertySets[prop_set].cProperties; prop++) I know in some cases to use sequences are wiser way than pointers, but so many of them are used in loops. Should I change them?
Optimizations should be primary for the human reader of the code. Compilers nowadays do a far better job at micro-optimization than humans.
bye michael
-
matyapiro31 -
Michael Stefaniuc -
Nikolay Sivov