coolprop.sm (4,64 KiB) scaricato 1375 volta(e).

This file uses CoolProp wrapper plugin to get some water property.
But between two invocations, a calculation is made that changes some state, so that after it any CoolProp calculation fails.

May it be that A() somehow mangles, say, FPU state (flags)? Like exeption masking, or somesuch?

Confirmed.

Wrote

This file uses CoolProp wrapper plugin to get some water property.
But between two invocations, a calculation is made that changes some state, so that after it any CoolProp calculation fails.

May it be that A() somehow mangles, say, FPU state (flags)? Like exeption masking, or somesuch?

I have a good idea about this plugin, having programmed WaterSteam in Visual basic
years ago. The plugin may be OK by itself but it suffers from the Smath silent
killer bug. Naturally, getting some properties uses some of the related constants.
Then, getting next properties does not renew constants previously used, and you get
any zombie result. Nothing to do untill this bug is cleared. The "clear" function
works, does not work.
If you work with WaterSteam, better get the freeware from "Katmar" [piece of gold].
Same formulation than IAPWS [quite monkey business inside IAPWS].
I programmed them in Mahcad 11, collab Fred was very happy.

Jean

Please don't reply: do this, do that
Smath does NOT do first, I don't have to do what it should do.

Fixed in Stable SMath Studio 0.98.5935.
Thank you.

Jean, thank you for pointing out the different behavior of Clear about built-in constants. My fault, was in my knowledge and I've forget to document it.
I've updated the plugin (SS 0.97.5346 and later), now the description of Clear(...) reflects also this behavior.

Wrote

Fixed in Stable SMath Studio 0.98.5935.
Thank you.

Once again, thank you very much Andrey.