Hi Pritpal, It's okay now, many thanks.
I've committed a minor optimization. It could be further optimized by using method like in FREAD(), or by using new Harbour API function hb_itemGetWriteCL(). These methods will prepare VM for passing buffers this way. Brgds, Viktor On Sun, Jun 28, 2009 at 5:50 PM, <[email protected]> wrote: > Revision: 11556 > > http://harbour-project.svn.sourceforge.net/harbour-project/?rev=11556&view=rev > Author: vouchcac > Date: 2009-06-28 15:50:14 +0000 (Sun, 28 Jun 2009) > > Log Message: > ----------- > 2009-06-28 08:44 UTC-0800 Pritpal Bedi ([email protected]) > * harbour/contrib/hbqt/hbqt.h > * harbour/contrib/hbqt/hbqt_qftp.cpp > * harbour/contrib/hbqt/hbqt_qhttp.cpp > * harbour/contrib/hbqt/qth/QFtp.qth > * harbour/contrib/hbqt/qth/QHttp.qth > * harbour/contrib/hbqt/TQFtp.prg > * harbour/contrib/hbqt/TQHttp.prg > ! Fixed ( char * ) argument usage in QFtp and QHttp classes. > Infact <qint64 read( char * data, qint64 length )> are written > as is in the header. I could not find a solution to > auto generate it because of <length> argument which could > never be known to first parameter. > > Modified Paths: > -------------- > trunk/harbour/ChangeLog > trunk/harbour/contrib/hbqt/TQFtp.prg > trunk/harbour/contrib/hbqt/TQHttp.prg > trunk/harbour/contrib/hbqt/hbqt.h > trunk/harbour/contrib/hbqt/hbqt_qftp.cpp > trunk/harbour/contrib/hbqt/hbqt_qhttp.cpp > trunk/harbour/contrib/hbqt/qth/QFtp.qth > trunk/harbour/contrib/hbqt/qth/QHttp.qth > > > This was sent by the SourceForge.net collaborative development platform, the > world's largest Open Source development site. > _______________________________________________ > Harbour mailing list > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour > _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
