> Looks like putting a sequential file in a dimensioned array makes it go out and reserve a block of memory the size of the entire file.
Doubtful.. I'm guessing under the hood the array will resolve to a series of pointers somewhere down the track, but those pointers will need to be cast to different types depending on what is being stored in the array - a variable, a file pointer, a sequential file pointer etc. So something in that cast will be wrong - it might for example be that whatever structure controls a sequential file originally contained a 32 bit address and now doesn't but the cast is still expecting that, or that it gets copied with an alignment change or something similar. In other words, typical C bug from a pretty unlikely occurrence. Brian _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
