Skip to content
Snippets Groups Projects
  1. Aug 10, 2021
  2. Jul 15, 2021
    • Jupp Tscheak's avatar
      Added possibility to register callback function when entity has been created/deleted. · 49e6a3d9
      Jupp Tscheak authored
      
      If scenario domain entities are having references to the same IEntity, it might be that another instance is deleting this IEntity invalidating all references pointing to it. Those situations could be handled using the callback mechanism.
      
      Signed-off-by: default avatarJupp Tscheak <jupp.tscheak@daimler.com>
      49e6a3d9
    • Jupp Tscheak's avatar
      Interface function IEntityRepository::Get is returning an optional reference to query an IEntity. · f1a2e347
      Jupp Tscheak authored
      
      In order to check whether an IEntity with a certain name/id exists, function IEntityRepository::Contains could be used to query this information. If IEntityRepository::Get is called on a non-existing name/id, the function would throw, so for defensive programming reasons a IEntityRepository::Contains should always be done before actually calling IEntityRepository::Get. The good thing about plain old C-pointers is that assignment and existence check can be done in one call. Since C++17 the same functionality is managed by std::optional.
      
      Another disadvantage of using a plain reference to IEntity is when it is used as a class member, where it needs to be initialized when an object of that class is defined. It might be that during construction time this IEntity is not known/existing yet. Of cource, a plain old C-pointer could be used in this case, but it wouldn't be a consistant usage.
      
      The proposal is to use std::optional<std::reference_wrapper<IEntity>> as return value for IEntityRepository::Get.
      
      Signed-off-by: default avatarJupp Tscheak <jupp.tscheak@daimler.com>
      f1a2e347
  3. Jul 08, 2021
  4. Jul 07, 2021
  5. Jun 18, 2021
  6. May 26, 2021
  7. Apr 06, 2021
  8. Mar 10, 2021
Loading