Re: [Dar-libdar_api] Poor performance of unlimited integer size
For full, incremental, compressed and encrypted backups or archives
Brought to you by:
edrusb
|
From: Denis C. <dar...@fr...> - 2018-08-10 11:49:17
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/08/2018 09:13, Tobias Specht wrote: [...] > > Hi Denis :) Hi Tobias! :) > > nice to hear you are improving the libdar API. Will have a look on > it. sure, so far all new API info is available GIT master, the doc/API_tutorial.html is up to date for example. I have removed all the pure C calls, replaces as much as possible arguments with standard types. In parallel, I also plan to make a C binding for those that do not want exceptions and classes... also planning a python-3 binding a bit like what Wesley Leggette did some years ago with python-2, but due to the longly expected 2.6.0 release this bindings will come right after this new major release. If you need any help to have gdar working with next to come release 2.6.0 tell me, I can provide support, of course! > > Best regards, Tobias Best Regards, Denis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIVAwUBW217tAgxsL0D2LGCAQh1+BAAkgKJeY+Sr6D1H9E8NO2F5Z5ksOnQe3TN 4s2PSVHRJuIAC1PU60Vl3RIcPtrUyO3XZuRLBdkLwRZlSZYtD69w20FODf7YfwB4 OiSAnsZP6dMkMjuNgBh7hB1/chIEnkZSmxtlqFCOwO+f+Ki1Xz2/CAARHzd3NgPo B0kUvBlVvNEFYFdyIh5uaMsbFbiUKkdR4QOZ/ROtdo0SfVoG+dRhcc7xu76aGnYw ylzVpnZmB02krd6XVpgMp4mnQLzCmjvD8cLAbUfBR2mU52McvJmlcPLSaRhp34xI XHai5LLAiSbykY3Sb64yb/7HQT/ZeHoYbsmMD1EeLEg0ohYN6GoPxGwWTrnDZ/H4 jM0K5oZmVEG8goQn1g3+juHW+T0i2Yxd4mSkPiryUxoJFzj8DmSww/AzEppeX+B+ OCk9vo6wegwXtHcv7nETX9pezMYN2HaFhLL/MzdOM3z4X2SZc5UEA0SZaI29IqUW 6tFDRsXnS0GQsZ4TgBNEc1vm1lDRXgYNpZuESbQNvkizjIUcZiHCk3Ri6ViY2n7M 9Q72o4hzroAx0YOF967FFdQj/8AXKzoMhWup/wCYiSsVCDBJjHtHcNXrvTGgEF2W ZgBrwdRVJZ4ClVGjEgWlM996TKE2AmdfngHZrYujO0FAY/eRBpxYmOILC0by1CaK g2e1qODzwrM= =0SEA -----END PGP SIGNATURE----- |