-
Notifications
You must be signed in to change notification settings - Fork 8
Name mangling #21
Comments
I agree that it would be great. More generally speaking, could it be a way to not overlap between coolprop and librefprop.so? |
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. |
Yeah, (something to define with them?), so we get the same headers everywhere :-) |
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. |
"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 :-). |
If the changes from commit CoolProp/CoolProp@4f52e52 and issues CoolProp/CoolProp#332 and CoolProp/CoolProp#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.
The text was updated successfully, but these errors were encountered: