librefprop.so Name mangling

If the changes from commit https://github.com/CoolProp/CoolProp/commit/4f52e5242a4536e68ab23e06c79b24632e0bbc64 and issues https://github.com/CoolProp/CoolProp/pull/332 and https://github.com/CoolProp/CoolProp/pull/335 do not throw any errors in the future, we would like to them here as well. The header files are a mess and it would be really nice to clean things up.

Dec 16 '14 09:12 jowr

I agree that it would be great. More generally speaking, could it be a way to not overlap between coolprop and librefprop.so?

Dec 17 '14 14:12 ghost

I am not sure what you refer to. CoolProp internally uses its own REFPROP headers and therefore does not require librefprop and its headers to be installed. You only need the librefprop headers if you would like to develop your own software that directly accesses REFPROP. There is no clash since CoolProp does not provide the REFPROP headers. No matter what, I agree that it would be ideal if CoolProp used the librefprop headers instead of its own version.

Dec 17 '14 14:12 jowr

Yeah, (something to define with them?), so we get the same headers everywhere :-)

Dec 17 '14 16:12 ghost

Who is 'them'? One way forward could be to just copy the headers from CoolProp. They work and they should be exactly the same from the programming point of view. Another possibility is to make this project and external dependency of CoolProp, just like Catch and Eigen. That would mean the main headers are here and tha CoolProp only pulls them for compilation. I'll create an issue over there.

Dec 17 '14 19:12 jowr

"Them" is coolprop devs ;-) ; Perfect, for the issue creation :-) I think it's a good thing to define a way to manage with them then stick to it :-).

Dec 18 '14 07:12 ghost