> On Thu, 14 Jan 2010, Szak�ts Viktor wrote: >>>> First actual question is what to do with ULONG in >>>> hb_fsSeek(). Should it be changed to HB_SIZE or not? >>> No. It cannot be HB_SIZE. It will be bug. The same is for other >>> functions like hb_fsWriteLarge(). All such functions have to use >>> parameters which are accepted by low level OS functions without >>> any size lost conversions. >> Okay, but what non-windows type to use then? int, long, else? > > As long as you do not update code which may use it then you should > use the same type 'unsigned long'. > In fact it will be good to eliminate hb_fs*Large() functions > and use only one set of functions using HB_FOFFSET as file pointer > and HB_SIZE as the block size but for this we should rewrite these > functions.
Looks perfect. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
