4 ms·

I wonder how, a typical #include "someLib/someLib2/someThing.h" would look like in a "tagging" world? Sorry, probably stupid example, but hierarchial has been

• ReleaseCandidat 5y ago
  > #include "someLib/someLib2/someThing.h" would look like in a "tagging" world #include "someLib/someLib2/someThing.h" Or whatever you choose as a delimiter for a hierarchy of tags. The biggest advantage is that you can use an (well ;) infinite number of tags to get to the same 'file' (without the hassle of needing to use symlinks), so that could also be #include "currentlyUsedLibs/someThing.h" and #include "foo/bar/baz/what/why/hmm/someThing.h" The problem isn't the hierarchy, but that there only exist a single (modulo symlinks) hierarchy to every 'file'. And that every sibling must have a distinct 'name' (the cat images in the article).
  • malkia 5y ago
    There is also the pecularity in the C++ preprocessor that it'll probe candidates among -I<folders> and pick first one that suceed. Now you would need to support this for "tagging" too. Not sure even how. It does not translate well I think. (Obviously I'm just complaining here, on the side of artists I think it was much easier for them (and for me actually, when comes to my own photos) to find things by tags - be it automatical, date, time, is it a document, location, etc.) - but then having to rely on consistent ("stable") name is going to be hard.