[Rivet] Dangerous casting to FinalState

[Andy Buckley]

Apologies, I meant abstract, i.e. non-instantiable due to at least one
declared but unimplemented method.

Andy


On 14/07/15 19:22, David Grellscheid wrote:
> 
>> For the following major release, it'd be good to solve this more
>> completely. FinalStates are the only significant subset of projections
>> which can have this problem, because FinalState itself is not virtual.
> 
> I don't understand what you mean here. Classes cannot be virtual /
> non-virtual, only methods can. A method is virtual if it has been marked
> so anywhere up the inheritance tree, it's not necessary to re-mark it as
> virtual in each child class.
> 
>   David
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> https://www.hepforge.org/lists/listinfo/rivet


-- 
Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
Particle Physics Expt Group, University of Glasgow