[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnucap-devel] modules/plugins/libraries

From: al davis
Subject: Re: [Gnucap-devel] modules/plugins/libraries
Date: Tue, 17 Sep 2013 09:46:05 -0400
User-agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; )

On Tuesday 17 September 2013, Felix Salfelder wrote:
> I get the following when loading a plugin
> > load ./
>        ^ ? ./ undefined symbol: SIM::outdata(double)
> SIM::outdata(double) comes from apps/, which is not
> part of but is
> this intended?

It was initially but it may have been an incorrect decision.  
The justification was that new plugins may want something 
completely different and plans to make outputs pluggable.

To be consistent, probably s__.h should have been left in apps, 
so you copy it to new plugins.

Plans were (and I think still are) to make this part into 
another tree of plugins, so you can have plugins for things like 
plotters, output formats, etc.

The thought was that for now, you can link to it explicitly when 
you build the plugin.  When the output plugins become available, 
the s_ plugins will need changes to accomodate the new features, 
but would still work the old way if you don't, without the 
obligation to keep the old interface in core.

Wishy-washy answer because I am not sure the decision was 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]