on memset

[Vincent SHAO]

int distance[MAX_X][MAX_Y];
memset(distance ,-2,MAX_X*MAX_Y*s izeof(int));

Academically, the buffer "distance" should have been filled with -2
after these two line,
but, memset just fail to do the trick, they are still a garbage value
"-16843010"

why?

Thank you.

[Ian Collins]

Vincent SHAO wrote:

int distance[MAX_X][MAX_Y];
memset(distance ,-2,MAX_X*MAX_Y*s izeof(int));

Academically, the buffer "distance" should have been filled with -2
after these two line,
but, memset just fail to do the trick, they are still a garbage value
"-16843010"

This isn't garbage, it's the correct result.

What units does memset work with?

--
Ian Collins.

[Alf P. Steinbach]

* Vincent SHAO:

int distance[MAX_X][MAX_Y];
memset(distance ,-2,MAX_X*MAX_Y*s izeof(int));

Academically, the buffer "distance" should have been filled with -2
after these two line,

No.

but, memset just fail to do the trick, they are still a garbage value
"-16843010"

why?

It seems your compiler creates program that use 32 bit two's complement 'int'.

In that case -2 is represented as bit pattern 0xFFFFFFFE, and as signed char
value, 0xFE, and filling an 'int' with byte value 0xFE gives you 0xFEFEFEFE,
which represents -16843010.

See the FAQ for more safe ways to represent matrices (or go directly to Boost
library).
Cheers, & hth.,

- Alf

[Vincent SHAO]

On 4ÔÂ16ÈÕ, ÏÂÎç2ʱ06·Ö, "Alf P. Steinbach" <[e-mail] wrote:

*VincentSHAO:

int distance[MAX_X][MAX_Y];
memset(distance ,-2,MAX_X*MAX_Y*s izeof(int));

Academically, the buffer "distance" should have been filled with -2
after these two line,

No.

but, memset just fail to do the trick, they are still a garbage value
"-16843010"

why?

It seems your compiler creates program that use 32 bit two's complement 'int'.

In that case -2 is represented as bit pattern 0xFFFFFFFE, and as signed char
value, 0xFE, and filling an 'int' with byte value 0xFE gives you 0xFEFEFEFE,
which represents -16843010.

See the FAQ for more safe ways to represent matrices (or go directly to Boost
library).

Cheers, & hth.,

- Alf

Thanks a lot.
And that is to say, i have to use double 'for' to init the buffer if i
want each elem in the buffer to be -2?

[Alf P. Steinbach]

* Vincent SHAO:

On 4?16?, ??2?06?, "Alf P. Steinbach" <[e-mail] wrote:

>*VincentSHAO :

>>int distance[MAX_X][MAX_Y];
memset(distan ce,-2,MAX_X*MAX_Y*s izeof(int));
Academicall y, the buffer "distance" should have been filled with -2
after these two line,

No.

>>but, memset just fail to do the trick, they are still a garbage value
"-16843010"
why?

It seems your compiler creates program that use 32 bit two's complement 'int'.

In that case -2 is represented as bit pattern 0xFFFFFFFE, and as signed char
value, 0xFE, and filling an 'int' with byte value 0xFE gives you 0xFEFEFEFE,
which represents -16843010.

See the FAQ for more safe ways to represent matrices (or go directly to Boost
library).

Cheers, & hth.,

- Alf

Thanks a lot.
And that is to say, i have to use double 'for' to init the buffer if i
want each elem in the buffer to be -2?

No.

The standard library has standard algorithms and even standard containers.

Perhaps the most straightforward (but see earlier advice) is

#include <vector>
int main()
{
using namespace std;
int const maxX = 2;
int const maxY = 3;
vector< vector<int distance( maxX, vector<int>( maxY, -2 ) );
// ...
distance[1][2] = 12345;
}

Cheers, & hth.,

- Alf

[Juha Nieminen]

Vincent SHAO wrote:

>>int distance[MAX_X][MAX_Y];
memset(distan ce,-2,MAX_X*MAX_Y*s izeof(int));

And that is to say, i have to use double 'for' to init the buffer if i
want each elem in the buffer to be -2?

Why is that a problem?

IMO it's a beginner's bad habit to try to make code as short as
possible (and achieving this by use of ugly tricks and hacks). Code
should be above all clear and well written. Shortness is completely
secondary (and usually irrelevant).

If you *really* want to use a "cool trick" to initialize that array
with one single loop, you can do this:

for(int i = 0; i < MAX_X*MAX_Y; ++i)
((int*)distance )[i] = -2;

However, that's ugly code and not recommended.

[Bo Persson]

Juha Nieminen wrote:

Vincent SHAO wrote:

>>>int distance[MAX_X][MAX_Y];
memset(dista nce,-2,MAX_X*MAX_Y*s izeof(int));

>And that is to say, i have to use double 'for' to init the buffer
if i want each elem in the buffer to be -2?

Why is that a problem?

IMO it's a beginner's bad habit to try to make code as short as
possible (and achieving this by use of ugly tricks and hacks). Code
should be above all clear and well written. Shortness is completely
secondary (and usually irrelevant).

If you *really* want to use a "cool trick" to initialize that array
with one single loop, you can do this:

for(int i = 0; i < MAX_X*MAX_Y; ++i)
((int*)distance )[i] = -2;

However, that's ugly code and not recommended.

It is also interesting to see what the compiler does for the
"unoptimize d" version with a double for loop:

; 8 : for (int i = 0; i != 1000; ++i)
; 9 : for (int j = 0; j != 1000; ++j)
; 10 : distance[i][j] = -2;

00001 mov eax, -2 ; fffffffeH
00006 mov ecx, 1000000 ; 000f4240H
0000b mov edi, OFFSET ?distance@@3PAY 0DOI@HA ; distance
00010 rep stosd
This code is
- easier to read
- faster than memset
- correct
Bo Persson