Esses correções de vazamento de memória "memory leak", o pessoal tinha se queixado disso.2014-03-06 18:15 UTC+0200 Pavel Tsarenko (tpe2/at/mail.ru)
* include/funcleto.h
* version number increased (2.13)
* include/srvleto.h
+ added last datetime read and write fields into AREASTRU and TABLESTRU
+ added bBufKeyNo and bBufKeyCount fields into USERSTRU
* include/rddleto.ch
+ added RDDI_BUFKEYNO and RDDI_BUFKEYCOUNT commands
* includeletocl.h
+ added ulKeyNo and ulKeyCount fields into LETOTAGINFO structure
+ added LetoSet() declaration
* source/server/letofunc.c
* source/client/leto1.c
* source/client/letocl.c
* source/client/letomgmn.c
* readme_rus.txt
* readme_pt_br.txt
* changed protocol for lock commands: if the table is modified by another
user after reading the record, together with the result of the lock
passed the changed record.
+ added RDDI_BUFKEYCOUNT and RDDI_BUFKEYNO commands, for buffering
ordKeyCount() and ordKeyNo() calls. Protocol for record data has been
changed: added KeyCount and KeyNo values.
2014-02-28 18:10 UTC+0200 Pavel Tsarenko (tpe2/at/mail.ru)
* source/server/letofunc.c
! memory leak
* source/client/letocl.c
* warnings
2014-02-27 17:55 UTC+0200 Pavel Tsarenko (tpe2/at/mail.ru)
* source/client/letocl.c
! fixed memory leak
2014-02-26 12:45 UTC+0300 Alexander Kresin (alex/at/belacy.ru)
* source/client/leto1.c
! letoTrans() was fixed to work correctly with an old sever version
Nenad,
according my personal checks:
LetoDB application have memory leaks(
checked with sir Valgrind in Linux.
Saudações,
Itamar M. Lins Jr.