For cosmetic (and obviously subjective reasons), use `:` when
appending a trigger name suffix.
Example:
-message-iterator-class-next-method:clock-class-is-expected-mii-mii
+message-iterator-class-next-method:clock-class-is-expected:mii-mii
I like it because it's now of the form:
<function name>:<cond id>:<suffix>
... where the suffix discriminates different triggers to reach the
pre/post condition identified by `<function name>:<cond id>`. When the
suffix is concatenated using `-`, it's not clear where the cond id ends.
Change-Id: I9e27524a589f19094eb90543d500d015a985a123
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/12779
Tested-by: jenkins <jenkins@lttng.org>
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
const bt2c::CStringView nameSuffix) noexcept :
_mType {type},
_mCondId {fmt::format("{}:{}", type == Type::Pre ? "pre" : "post", condId)},
- _mName {fmt::format("{}{}{}", condId, nameSuffix ? "-" : "", nameSuffix ? nameSuffix : "")}
+ _mName {fmt::format("{}{}{}", condId, nameSuffix ? ":" : "", nameSuffix ? nameSuffix : "")}
{
}
* ID `condId` (_without_ any `pre:` or `post:` prefix), and the
* optional name suffix `nameSuffix`.
*
- * The concatenation of `condId` and, if it's set, `-` and
+ * The concatenation of `condId` and, if it's set, `:` and
* `*nameSuffix`, forms the name of the condition trigger. Get the
* name of the created condition trigger with name().
*/