Klemens Böswirth
Klemens Böswirth
> > const [...] implies certain things to the consumer of the API, chiefly that the data behind the pointer won't be modified. > > No, I don't think that...
> That is a very general question In my mind the question has a very simple answer. `const` in C means read-only, i.e. data that cannot be modified. [The](https://learn.microsoft.com/en-us/cpp/cpp/const-cpp?view=msvc-170) internet...
> The relevant question is from which viewpoint it is read-only. I was pretty clear on that IMO. The data is read-only, and my links basically agree there. For a...
Everything you mentioned would be implemented in `Key`. But related to this there is also: - [ ] A `KeySet` can either contain only `meta:/` keys, or no `meta:/` keys....
The `ni` uses a 3rd party ini library. I'm not sure how easy it would be to change the key value separator from `=` to `:=`. Regarding the `meta:/` prefix....
@markus I think this could be a good FLOSS issue. Stripping the `meta:/` prefix when writing and adding it when reading should be pretty simple.
I'm not sure, whether this is the issue but this line in `mountpoint-info.sh` is definitely wrong (`:` is missing): https://github.com/ElektraInitiative/libelektra/blob/7cba2f97152ce272307a14fe95232394b80b181d/scripts/kdb/mountpoint-info#L18 The `sed` error is probably from the second `sed` in...
> In sed you can use (nearly) any character as "separator". I know. It's also not easy to escape the chosen separator in a shell script. That's why I suggested...
The script definitely needs to be updated for `new-backend`, if we want to keep it at all. Since different backends can have different positions, I think we should just remove...