[Rivet] Plugin Projections

Leif Lönnblad leif.lonnblad at thep.lu.se
Tue May 3 09:25:22 BST 2011


On 2011-05-03 10:09, David Grellscheid wrote:
>> You *might* be able to write a new projection and build it into an
>> analysis plugin, because then the only code that is using that
>> projection will have been able to see its interface while being
>> compiled. I have a vague feeling that I *have* done that before, but if
>> I did it was a long time ago!
>
> We do this for NQN all the time, it works very well. As long as you put
> the projection code into the .so together with the analysis, there are
> no problems.

Isn't there is a potential problem if you want to use the same 
projection in more than one analysis module? I would think it would be 
difficult to for the dynamic linker to have the same code in two 
different .so files, although I haven't tested it. This would be solved 
if the projection is compiled in a separate .so plugin file, although 
the for loading analysis plugins would become a bit more cumbersome.


/Leif




More information about the Rivet mailing list