keyGetBaseName

• start = 2021-03-04 21:05
• end = 2021-03-04 21:35
• reviewer = Stefan Hanreich stefa.nosp@m.nhan.nosp@m.i@gma.nosp@m.il.c.nosp@m.om

Signature

ssize_t keyGetBaseName(const Key *key, char *returned, size_t maxSize)

Checklist

Doxygen

(bullet points are in order of appearance)

• [x] First line explains briefly what the function does
• [ ] Simple example or snippet how to use the function
  
  • [ ] add
• [ ] Longer description of function containing common use cases
  
  • [ ] add description of what happens when maxSize < baseNameSize
• [x] Description of functions reads nicely
• [ ] @pre
  
  • [ ] add
• [ ] @post
  
  • [ ] add
• [ ] @invariant
  
  • [ ] add
• [x] @param for every parameter
• [x] @return / @retval
• [ ] @since
  
  • [ ] add
• [x] @ingroup
• [ ] @see
  
  • [ ] split first line
    
  • [ ] maybe remove second line?

Naming

• Abbreviations used in function names must be defined in the Glossary
• [x] Function names should neither be too long, nor too short
• [x] Function name should be clear and unambiguous
• Abbreviations used in parameter names must be defined in the Glossary
• [x] Parameter names should neither be too long, nor too short
• [ ] Parameter names should be clear and unambiguous
  
  • [ ] change to returnedBaseName in order to be more in line with other
    functions?

Compatibility

(only in PRs)

• Symbol versioning is correct for breaking changes
• ABI/API changes are forward-compatible (breaking backwards-compatibility to add additional symbols is fine)

Parameter & Return Types

• Function parameters should use enum types instead of boolean types wherever sensible
• [x] Wherever possible, function parameters should be const
• [x] Wherever possible, return types should be const
• [x] Functions should have the least amount of parameters feasible

Structural Clarity

• [x] Functions should do exactly one thing
• [x] Function name has the appropriate prefix
• [x] Order of signatures in kdb.h.in is the same as Doxygen
• [x] No functions with similar purpose exist

Memory Management

• [x] Memory Management should be handled by the function wherever possible

Extensibility

• [x] Function is easily extensible, e.g., with flags
• [x] Documentation does not impose limits, that would hinder further extensions

Tests

• [ ] Function code is fully covered by tests
  
  • [x] Lines 1147:1148
• [ ] All possible error states are covered by tests
  
  • [x] Lines 1147:1148
• All possible enum values are covered by tests
• [x] No inconsistencies between tests and documentation

Summary

add more tests for special cases? (spaces, escaped slashes,...)

Other Issues discovered (unrelated to function)