Hi Julia, Since approximately version 4.4.0, FieldIO is an abstract class which cannot be instantiated, indicated by e.g. FieldIO::GetClassName being pure virtual: LIB_UTILITIES_EXPORT virtual const std::string &GetClassName() const = 0; This is not related to the missing default argument. In case you want to read/ write fld files, use FieldIOXml instead of FieldIO and it should work: LiibUtilities::FieldIOXml fIO(vSession->GetComm()); Let me know if it does not (I didnt test it). Cheers, Kilian Am Mittwoch, 5. Juli 2017, 17:03:20 CEST schrieb Julia Docampo (MTH):

Hello:

I noticed some changes in the newest nektar version in the FieldIO class (?). This class had the constructor option:

LIB_UTILITIES_EXPORT FieldIO(LibUtilities::CommSharedPtr pComm,

bool sharedFilesystem = false);

However, it is not there in the new one... I have a solver that uses this constructor like this LiibUtilities::FieldIO fIO(vSession->GetComm)) ie, with the default argument false. With the new version, there is no default argument but if I try to force the condition: fIO(vSession->GetComm,false)) I get errors $: cannot declare variable ‘fIO’ to be of abstract type ‘Nektar::LibUtilities::FieldIO’

How can I use this constructor like for the previous version?

Thanks

- Julia

-- Kilian Lackhove, M.Sc. Fachgebiet für Energie- und Kraftwerkstechnik L1|08 114 Technische Universität Darmstadt Jovanka-Bontschits-Straße 2 D-64287 Darmstadt Germany Tel.: +49 6151 16 - 28915 Fax: +49 6151 16 - 6555 e-mail: lackhove@ekt.tu-darmstadt.de