Skip to content
This repository has been archived by the owner on Mar 29, 2019. It is now read-only.

Name mangling #21

Open
jowr opened this issue Dec 16, 2014 · 5 comments
Open

Name mangling #21

jowr opened this issue Dec 16, 2014 · 5 comments
Milestone

Comments

@jowr
Copy link
Owner

jowr commented Dec 16, 2014

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.

@ghost
Copy link

ghost commented Dec 17, 2014

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

@jowr
Copy link
Owner Author

jowr commented Dec 17, 2014

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.

@ghost
Copy link

ghost commented Dec 17, 2014

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

@jowr
Copy link
Owner Author

jowr commented Dec 17, 2014

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.

@ghost
Copy link

ghost commented Dec 18, 2014

"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 :-).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant