I have this struct:


This is being used to map the block of memory occupied by skill[0..99] over the Foo structure.

Oddly, this works sometimes and others it returns NULL!?!?

Seems to be a weird casting issue with the skill array.

Can anyone tell me why this happens?

Pointers make my head hurt, but a quick look suggests to me that
you are trying to map an array of VAR's (the entity skills) over the
top of a structure of varied elements (two ints and a float).
VARS, INTs and FLOATs are stored in four bytes of memory, BUT the
format they are store in varies greatly.
Your concept could 'possibly' work while all the values are zero,
but after that, all bets are off.

Change your struct to be all VARs and it looks to be workable.

Thanks for the info, evil.

I would still like to learn *why* it doesn't work (maybe post this in 'ask the devs'?).

Since a 'var' is 4 bytes, e->skill should be a pointer to a block of 400 bytes. Why shouldn't this work every time?

The semantics of Lite-C seem to second guess the developer, or at least it appears so.

It will be a block of 400 bytes, but each 4-byte block is going to
be expected to be in the VAR format when looked at from the skills angle,
and will be expected to be INT or FLOAT format when looked at from the struct side.
By 'type' format I mean which of the 4 bytes is the Most-Signifigant byte,
which is the least, which is a multiplier and that sort of thing.

Its not a lite-c thing, its a true C thing. Try looking around some C or C++
tutorial sites and you may find how INTs and FLOATs are internally structured,
but you'll need to ask the Devs about how the VAR is structured.