Added protection to overflow on malloc argument. Decided not to implement logging.

1 files changed, 0 insertions, 5 deletions

diff --git a/readme.md b/readme.md
index b89a593..4fef661 100644
--- a/readme.md
+++ b/readme.md
@@ -1,10 +1,6 @@
 Task Time Tracker
 =================
 
-# notes
-- Only one task may be active;
-- The log will be a circular array. During app startup the array will be loaded from a csv file. The log array should have a fixed length. Each string in the array should also have fixed length. Loading and storing it to a file will be implemented using readline and writeline operations. In order for the log file to be CSV compatible, we must always use the same format when writing to the log array. Best approach is to use a function that enfores the CSV format. The log should be written to a file every 5 minutes (not set in stone), if required; such may be done using a `log_is_dirty` flag. A possible structure for the log entries is: {uint64_t timestamp; uint8_t action[16]; uint8_t task_name[MAX_TASK_NAME+1]; uint8_t notes[16]; }.
-
 # know-how
 - [ncurses colors](https://tldp.org/HOWTO/NCURSES-Programming-HOWTO/color.html#COLORBASICS)
 - [pprintf](https://cplusplus.com/reference/cstdio/printf/)
@@ -55,7 +51,6 @@ Task Time Tracker
 - [x] Add/remove time using keys: `F3`;
 - [x] Add/remove time for any day of week;
 - [x] Total times may saturate, but before that the user will see the infinite symbol. Solution: Provide user with possibility to refresh totals.
-- [ ] Implement logs as described above.
 - [ ] Improve the way we save the changes made to the database:
 	- When operating on the archive, will we keep the saves synchronous?
 	- Maybe add a cooldown timer and save changes after it times out?