[galap]

Since OF2.2 there are a lot of changes to the thermophysicalModels. We are running libs here derived from basicThermo which requires now the specification of several virtual functions. I want to solve this by returning NULL pointer fields. Unfortunately I am not able to clearify how a NULL volScalarField can be returned. Does anyone know this?

Thanks in advance

[ngj]

Hi Fabian,

In such cases, where certain functions need implementation, but I know that they will never be used/does not make sense, I use the following in the source code:

notImplemented("<some string describing the issue>");

This will terminate the simulation with a FatalError, so cleaner than making the program work on NULL-pointers. With respect to the return type, then I simply ignore the warnings in the compilation, since the program will never reach

return <some object>;

Kind regards

Niels

[thomasArk47]

Hi,

return volScalarField::null();

works fine (as well for volScalarField than for tmp<volScalarField>)

[galap]

I met again this issue. The ::null() actually works, but I have problems to check, whether it is set or not.

What I am using now is: (schematic)

void request_data(autoPtr<volScalarField> data)
{
    if (..) { data.set(&<object-you-want-to-return>); }
    else { data.clear() }

    return data;
}


in main script:

autoPtr<volScalarField> data;
request_data(data);

if (data.valid()) { .... }

Maybe this helps someone

[galap]

Be aware that autoPtr takes over control of the prior associated pointer. Instead of autoPtr its better to use tmp. You can use the same syntax, just replace autoPtr with tmp. Instead the set function you have to use data = tmp<volScalarField>(&<object-you-want-to-return);