Re: size problems when casting integer onto set in gpc

>
> I think you should write what you really want to do.  If you want
> copy content of a set to an array of 16-bit integers (or back) you
> can use Move builtin routine.

That's exactly what I want to do. The move command seems to work and 
so I have managed to create an array of 16-bit integers sized at 14-
bytes total. The problem still arises however, when I try to cast/
write this array onto a 112-element set. Firstly due to the set being 
worth 16 bytes in 32-bit gpc. Secondly as the two items are not the 
same 'shape' in memory I get a crash on execution.

I have tried re-sizing the array of 16 bit integers to have an extra 
'blank' row, to bring its size up to 16 bytes. This removes the 'cast 
to type of different size' warning. However still crashes with 
segmentation errors on running, perhaps due to memory "beyond 
allocated size" as you say.

Generally, what determines the size/shape of memory allocated for a 
set or an array?

Concerning crash: accessing memory
> beyond allocated size is likely to cause crash (in newer gpc versions
> most such cases should be caught by range checking).

Do you happen to know which 'newer' gpc version will work smoothly in 
conjunction with gcc?


Thanks again