[Rivet] Dangerous casting to FinalState

[Chris Pollard]

Hi David, all,

Before responding below, can I solicit opinions from David and Frank on
whether we should move forward with the release? This still looks like a
complicated issue to me that needs more time...

          In that case we would need to understand why
>>>          VetoedFinalState remainder = zfinder.remainingFinalState();
>>>          addProjection(remainder, "RFS");
>>>          (i.e. making a full copy, not just by reference)
>>>          makes Rivet's projection book-keeping fall over:
>>>
>>>          Error in MY_RFSTEST2c::init method: No projections registered
>>>          for
>>>          parent 0x7ffe07be8840
>>>
>>
> I guess that's because we don't have a dedicated copy constructor that
> re-registers the copy with the handler. This now would be a valid reason to
> ban copies completely, but needs to be done consistently throughout the
> projection machinery.


Do we have other options? Isn't it possible to check with the handler
whether the projection-being-copied already has been registered and, if so,
register the new projection as well?

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20150710/c54841b7/attachment.html>