protections for the case CbmEvent::GetNofStsTracks() == -1

protections for the case CbmEvent::GetNofStsTracks() == -1

In the code, it is usually assumed that CbmEvent::GetNofStsTracks() >= 0, while it may be -1.

Actually, CbmEvent::GetNofData(ECbmDataType type) never returns 0.

There is no way to "register" a data type in CbmEvent without adding some data of the type. When there is no data of a type, it returns -1. If there is data, it returns >= 1.

Maybe we should change the convention for CbmEvent::GetNofData(ECbmDataType type) and return 0 when there is no data.

requested review from @v.friese

assigned to @se.gorbunov

Dear @i.selyuzhenkov, @f.uhlig, @v.friese, @p.-a.loizeau, @se.gorbunov, @v.akishina,

you have been identified as code owner of at least one file which was changed with this merge request.

Please check the changes and approve them or request changes.

added CodeOwners label

I will change CbmEvent to return size_t for GetNofData(...). So your checks here would not be necessary.

The original conception was that branches are registered by respective tasks, but that was never carried out, and is, I think, also not necessary.

@v.friese, ok, then I close this MR.

closed

See !1286 (merged).