1. 27 Oct, 2020 1 commit
  2. 06 Oct, 2020 2 commits
    • Karel Koci's avatar
      LogC version 0.1.0 · c05023fd
      Karel Koci authored
      Initial version of logc with limited support and unstable API
      c05023fd
    • Karel Koci's avatar
      configure: fix some warnings by autoreconf · bbf03b17
      Karel Koci authored
      It should have been chosen by configure what distribution formats should
      be in default generated instead of forced in Makefile.am.
      This also fixes warning from Makefile.am.
      bbf03b17
  3. 26 Sep, 2020 1 commit
    • Karel Koci's avatar
      configure: disable tests and linter by default · 8ea2adae
      Karel Koci authored
      It is common to build project just by running ./configure && make &&
      make install. It is inconsistent to enable tests and linter in such case
      as that introduces unnecessary dependencies. Instead for development we
      can enable these.
      8ea2adae
  4. 16 Sep, 2020 1 commit
    • Karel Koci's avatar
      Add Gitlab CI · 57c3f8db
      Karel Koci authored
      This includes test to compile project, to run tests in various
      environments and code coverage.
      57c3f8db
  5. 20 Aug, 2020 3 commits
    • Karel Koci's avatar
      07638e0a
    • Karel Koci's avatar
      logc: rework default format to better handle colors · 90bccc81
      Karel Koci authored
      This also adds tests for colors in formats defined in logc header.
      90bccc81
    • Karel Koci's avatar
      logc: fix how level condition work and add origin setting · f9b8c67a
      Karel Koci authored
      There was a collision in design of conditions that we can either check
      for level of output or for level of message. It makes much more sense to
      have it depending on level of message so it was converted to that. That
      also fixes usage with colors.
      
      That opened up question on how to handle other case when we do want to
      check for setting of logger rather message. In the end it seems like the
      only reason why we would want to do this is to print additional trace
      info and that is origin of message. Because of that this replaces that
      usage with dedicated option that does exactly that.
      
      In future we might return to original design and introduce both
      condition. Even in such case it makes sense to not tie origin print to
      level of logger as with not yet implemented design of subordinate
      loggers it is going to be less clear if user really wants to trace or
      just wants higher level to see also subordinate messages.
      f9b8c67a
  6. 18 Aug, 2020 1 commit
    • Karel Koci's avatar
      logc: fix order of inclusion to protect only if DEFLOG is defined · 441e93ee
      Karel Koci authored
      This is much better user wise as it is no longer required to have DEFLOG
      defined before first inclusion of logc.h. Instead now there just have to
      be only one DEFLOG definition before any logc.h inclusion. That makes it
      so multiple inclusions before DEFLOG definition do not affect inclusion
      of these macros.
      441e93ee
  7. 11 Aug, 2020 5 commits
  8. 10 Aug, 2020 3 commits
  9. 29 Jul, 2020 2 commits
  10. 14 Jun, 2020 2 commits
    • Karel Koci's avatar
      logc_assert: move assert function to separate header · 41b8748b
      Karel Koci authored
      It makes sense for users to just selectively use just assert. Including
      it in logc_util forces them to include all utility macros as well. This
      way it makes it really assert.h like replacement.
      41b8748b
    • Karel Koci's avatar
      logc_util: add std_fatal · 349d003d
      Karel Koci authored
      This is intended to cover cases when failure is unlikely but still
      possible while covering it is impossible and/or waste of time.
      349d003d
  11. 12 May, 2020 2 commits
  12. 11 May, 2020 2 commits
    • Karel Koci's avatar
      logc: add log_would_log function · bda6cb79
      Karel Koci authored
      The idea is to allow user of LogC to check if preparation of output even
      makes sense.
      
      This should be used when user wants to run some time consuming data
      collection and assembly to put together message. Such process can be
      just skipped if it would not be used anyway.
      bda6cb79
    • Karel Koci's avatar
      logc_argp: add argp based parser · d132b5e9
      Karel Koci authored
      This is extension library to add option to configure logging for
      application.
      
      This requires argp parser to be used for argument parsing.
      d132b5e9
  13. 07 May, 2020 3 commits
  14. 06 May, 2020 4 commits