Comment #7 on issue 3654 by [email protected]: Wrong relative path to
v8-platform.h in include/libplatform/libplatform.h
https://code.google.com/p/v8/issues/detail?id=3654
I'm not sure that I understand it.
It's fine, one can move it somewhere else, what does it break?
There are two sets of files, public headers for the library clients, and
private headers and cpp files which are only for the library itself. Public
headers are in 'v8_root/include' and they don't include any of the private
header. As I see private headers and cpp files are in ''src/libplatform''
and they include private headers and public headers. You may do what ever
you want with your private files, nobody cares. Using relative paths in
public headers the library as well as the library client are still
compilable, but the library client does not have to care about the
directory structure of the project.
If you rearrange your code in public headers anyway the client has to
change the code.
So, why are the relative paths in public headers a bad idea?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
