Working on the ncstats bindings I found something interesting:
Without banners, If I don't call notcurses_stats after allocating a new ncstats object, the preallocated number of renders is absurdly high.
With banners, If I don't call notcurses_stats after allocating a new ncstats object, the preallocated number of renders is 0. I guess that's expected.
I also want to confirm whether I should use free to deallocate the ncstats objects before the end of the program. In that case maybe they ought to have have a destroy function?
Working on the ncstats bindings I found something interesting:
notcurses_stats
after allocating a newncstats
object, the preallocated number of renders is absurdly high.notcurses_stats
after allocating a new ncstats object, the preallocated number of renders is 0. I guess that's expected.I also want to confirm whether I should use
free
to deallocate thencstats
objects before the end of the program. In that case maybe they ought to have have a destroy function?I made a small C program:
results