Clarification requested for L_FileInfo and the FILEINFO data structure

Hello.  I'm currently using version 13 of the Raster Imaging
API.  I have a question concerning the use of the L_FileInfo
function.  This function takes a pointer to a FILEINFO data
structure.  Does this data structure need to be zero initialized
before calling the L_FileInfo function?  What behavior can occur
if it is not zero initialized?  The documentation and many
examples suggest it doesn't require pre-initialization, however, I've
experienced random behavior in some cases when it is not zero initialized.

// sample that produces random crashes and failures
FILEINFO fileInfo;
int iRet = L_FileInfo( "test.jpg", &fileInfo, 0, NULL );


// sample that doesn't appear to produce any crashes or unexpected behavior
FILEINFO fileInfo
memset( &fileInfo, 0, sizeof( fileInfo ));
int iRet = L_FileInfo( "test.jpg", &fileInfo, 0, NULL );



Is the FILEINFO data structure used as both an input and output
argument?  Since it is easy enough to just go ahead and zero
initialize the data structure before calling L_FileInfo, I simply do
that.  I'm looking for clarification that doing so does indeed fix the random crashes we sometimes experience.

Thanks for any feedback.

Rick Bray

There are 2 main uses for this structure:

1. To get file information using L_FileInfo. In this case, no need to initialize it with specific values because the function will fill it.
2. To provide information to a file loading function, such as L_LoadBitmap. If you use it this way, you must provide correct information and correct flags. For example, if you want to tell the function that you know the file type, set FileInfo.Format to the file type and set FileInfo.Flags to FILEINFO_FORMATVALID.

In any case, it's always good programming practice to fill structures with zeroes and to initialize pointers to NULL, to help you catch any hidden bugs that might creep into your code. For example, you don't the FileInfo.Flags to contain the FILEINFO_FORMATVALID value when you are not really supplying the correct format in FileInfo.Format