Enable relative namespaces

[numeredev]

SUMMARY

Implements necessary changes for #18

Reviewers: @numere-org/maintainers

IMPLEMENTATION

• Implementation: Implemented as proposed by the analysis.
• Implementation test: Called a procedure using the relative naming convention, used the tooltips, calculated the dependency. No problems detected.

DOCUMENTATION

• [x] ChangesLog updated
• [x] Code changes commented
• Documentation articles:
  • [x] corresponding documentation articles updated
  • [ ] new documentation articles created
  • [ ] not needed
• Language files:
  • [ ] corresponding language files updated
  • [x] not needed

---

TESTS BY REVIEWERS

• [x] Added to the automatic SW tests
• [x] Tested manually

[numeredev]

Three different features to test here: the relative namespaces, the RegEx functionality of TAB().fndcols() and the new string function getfilediff().

• Tests for getfilediff(): check only, if the return value has a length, if (a) both files exist, (b) one string is an empty string and (c) one file does not exist
• Tests for TAB().fndcols(): There are already tests for this method. Just add some basic RegEx test for that (Note that it is using a regex search not a match, i.e. also only matching substrings are valid)
• Tests for the relative namespaces: This might require another namespace in the SW test repo, which then can be called from the procedure tests. It should be possible to address a relative namespace with two ~ after each other, e.g. $goto~~relative~namespace(), if the current procedure is in goto and the called $namespace() is in relative next to goto (~~ can be interpreted as /../ in folder paths)

[diop7]

getfilediff() and $goto~~ tested manually TAB().fndcols() tested automatically

[diop7]

Added newNamespace~relativeNamespace