Who is not also a little bit (how much?) confused with kB and KB.
Programming computers you can produce a lot of minor and major errors
in your code, if you don't pay attention.
The following example should demonstrate this as far as an example
can:
#define K ...
#define k ...
main{}
{
char buffer[k];
for (i=0;i<FILESIZE;i+=k) {
read(FILE,buffer,K);
}
}
A) k=1000, K=1024 : SIGSEGV
B) k=1024, K=1000 : dma-problems byte-boundary, confusing code,
wasting memory (Hello Microbesoft)
C) k=1000, K=1000 : dma-problems byte-boundary, confusing
D) k=1024, K=1024 : Perfect -> use this with Linux
Wasting also time in translating 10^x to 2^x and vise versa I would
suggest to:
- Use hexadecimal or octal values for marking informations (for them
they has been intented)
- We should learn to calculate with hex or octal numbers rather than
decimal. Time ago a base of 12 has been used, that means a change
can be arranged. Maybe this looks a little bit strange, but when
you are used to calculate with hex, it work as well as decimal.
.................ciao
-- Since technology has became more solvent, the overheat grew dued to the possibility of more adaptivity and flexibility of the systems. This anew caused the wish of a much more solvent technology, because the new technologies more on both global effectivity and local comfortability has been discovered. Now the technology is solvent enough, to get on well with the higher overheat. What should we do now? D. Kaeppel ___ mailto:tires@nuernberg.netsurf.de __________________________________