GScanner leaking fd - by design ?



In glib/gscanner.c there are various places where
scanner->input_fd is set to -1

Current Gimp cvs (compiled on win32) triggers 
the one in g_scanner_get_char() and as a result looses
it's reference to the input file.

Is it an error in the usage of GScanner or should the
input_fd simply not be used as persitent during the
scanning phase ?
Shouldn't there be at least a g_warning when GScanner
destroys the input_fd reference ?

Thanks in advance,
	Hans

-------- Hans "at" Breuer "dot" Org -----------
Tell me what you need, and I'll tell you how to 
get along without it.                -- Dilbert



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]