Sure Dick, Seems that fseek returns 0L, as that is where the internal buffer points. The setvbuff destroys the internal buffer and when is used the read call, file operations begins where the buffer manager has leaved the real file descriptor (6k ahead).
Being the read already buffered, #ifdef it out has almost no impact on performance. Hoping this makes now more sense, -- Marco On 06/dic/2012, at 19:17, Dick Hollenbeck wrote: > On 12/06/2012 12:03 PM, Marco Serantoni wrote: >> On 27/nov/2012, at 15:29, Dick Hollenbeck wrote: >> >> Dick, >> Sadly it doesn't work, i'll just revert to the old code and add an #ifndef >> to exclude the setvbuff call. > > ftell() is returning 0? > > >> Cleaner and simpler :) > > Nonsense. > > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
