{"push_id":795619936,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ee07a735de08a456655fc520bb013d0c4dd2b562","before":"026408a2bb76a0950f27afcae248ef0381fd45dd","commits":[{"sha":"ee07a735de08a456655fc520bb013d0c4dd2b562","author":{"email":"4bfcf7061e9ba796b9dcff967c277d0843382033@poczta.onet.pl","name":"Przemysław Czerpak"},"message":"2015-09-17 12:23 UTC+0200 Przemyslaw Czerpak (druzus/at/poczta.onet.pl)\n  * include/hbapicls.h\n  * src/vm/classes.c\n    * minor modification in variable name\n\n  * src/rtl/filebuf.c\n  * src/rtl/fscopy.c\n  * src/rtl/fslink.c\n  * src/rtl/vfile.c\n    * cleaned FError() setting. It should not be changed by C file IO\n      functions because they can be activated from RDD code so accessing\n      work area field could change the FError() result, i.e. this code\n      does not work when FError() is changed by C level IO operations:\n         AnyFunc( FSeek( hFile, 0, FS_END ), field->MEMOVAL, FError() )\n      Even simple field access may cause file IO operations in RDD code\n      when relations are set because records in child area are repositioned\n      only when necessary (when user tries to make some operations on this\n      area). In the past RDD code was full of constructions like:\n         uiSaveError = hb_fsFError();\n         // make some IO operations\n         hb_fsSetFerror( uiSaveError );\n      to eliminate such overhead I separated PRG level FError() from\n      C level IOError(). Please keep it.\n\n  * ChangeLog.txt\n    ! few typos","distinct":true,"url":"https://api.github.com/repos/harbour/core/commits/ee07a735de08a456655fc520bb013d0c4dd2b562"}]}