[Kst] Compilation problem with the netcdf datasource

[Peter Kümmel]

nicolas.brisset at free.fr wrote:
> Hi,
> 
> I've started looking at the recent changes on datasources. I haven't come very far yet, but I have noticed the following compilation problem on OpenSuse 11.2:
> 
> compiling kstnetcdf.cpp
> kstnetcdf.cpp: In member function ‘virtual const Kst::DataVector::Optional DataInterfaceNetCdf::optional(const QString&) const’:
> kstnetcdf.cpp:69: error: in C++98 ‘opt’ must be initialized by constructor, not by ‘{...}’
> kstnetcdf.cpp:69: warning: extended initializer lists only available with -std=c++0x or -std=gnu++0x
> kstnetcdf.cpp:69: error: no matching function for call to ‘Kst::DataVector::Optional::Optional(<brace-enclosed initializer list>)’
> ../../libkst/datavector.h:60: note: candidates are: Kst::DataVector::Optional::Optional(int, int)
> ../../libkst/datavector.h:59: note:                 Kst::DataVector::Optional::Optional()
> ../../libkst/datavector.h:58: note:                 Kst::DataVector::Optional::Optional(const Kst::DataVector::Optional&)
> kstnetcdf.cpp:75: error: ‘struct Kst::DataVector::Optional’ has no member named ‘vectorframeCount’
> 
> I have tried adding the -std=gnu++0x flag: the first message disappears, but not the second one. I will skip that datasource for now, but that also means I can't test it :-(

My fault, haven't build on Linux after last changes on Windows. It's fixed now.

> However, from what I see it looks rather good: good job, Peter! The only problem is that I'm really going to have to learn more C++ to be able to understand more of that, because as it is I'm a bit overwhelmed. But I'm not a (real) programmer, so that does not mean you have to worry that the changes done are not clear :-)
> 
> That said, I have lots of issues at the moment with the ASCII datasource, which have a higher priority. But that will be the topic for another mail, or even a bugreport. It's even next on my todo list, as it is really bugging us and preventing the use of recent trunk versions.

OK, then I'll have a look at ascii datasource next.

Peter