-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing header extension from .h to .hpp #653
Conversation
… existing code base
Conflicts: dart/constraint/ConstraintSolver.cpp dart/constraint/ConstraintSolver.h dart/utils/SkelParser.cpp
…ects that sharing dart::Shape
… same associated object -- not completed yet
…shapenode Conflicts: apps/rigidShapes/Main.cpp dart/collision/bullet/BulletCollisionDetector.cpp dart/collision/bullet/BulletCollisionNode.cpp dart/collision/bullet/BulletCollisionObjectData.h dart/collision/dart/DARTCollisionDetector.cpp dart/collision/fcl/FCLCollisionDetector.cpp dart/collision/fcl/FCLCollisionNode.cpp dart/collision/fcl/FCLCollisionObjectData.h dart/collision/fcl_mesh/FCLMeshCollisionNode.cpp dart/utils/SkelParser.cpp dart/utils/sdf/SoftSdfParser.cpp tutorials/tutorialBiped-Finished.cpp tutorials/tutorialBiped.cpp unittests/testConstraint.cpp
Conflicts: CMakeLists.txt apps/rigidShapes/Main.cpp dart/constraint/ConstraintSolver.cpp dart/constraint/ConstraintSolver.h tutorials/tutorialBiped-Finished.cpp tutorials/tutorialBiped.cpp unittests/testConstraint.cpp
…type until we have actuator semantics
Conflicts: dart/utils/SkelParser.cpp
…o CollisionGroups
…nt libraries depending on dependency 3rd party library requirements
…osgdart Conflicts: CMakeLists.txt osgDart/CMakeLists.txt
Conflicts: CMakeLists.txt appveyor.yml ci/script_linux.sh ci/script_osx.sh dart/gui/osg/examples/CMakeLists.txt tutorials/CMakeLists.txt
In a day or two I'll have a pull request coming in related to #643 where we end up with some new files and remove some old ones. That'll be guaranteed to have merge conflicts with this. I suggest we hold off on renaming files and renaming "DART" instances until we've 100% finalized DART 6.0. Otherwise we'll probably end up with ugly merge conflicts and needing to duplicate efforts. Also, I'm not sure if we should rename the file extensions in DART 6.0. I was thinking we might just want to rename the extensions for KIDO to simplify the API incompatibility between DART 5 and DART 6. |
Right, I'll try to resolve the merge conflict once your PR for #643 is merged (or created) since I already put some efforts already. 😓 Another concern I have is the conflicts between #631 and
I thought we intend to minimizing the difference in transitioning from DART 6.0 to KIDO 7.0 (just name change). I'm a bit inclined to making this change in DART 6.0 because the incompatibility of file extension can be straightforwardly resolved by including |
That's a fair point. An alternative might be to "deprecate" the I suppose I'm okay with it either way. No matter what, it'll be like ripping off band-aid; it's painful but needs to be done sooner or later.
It won't be a trivial merge, but I don't believe it will be very painful either. Any merge conflicts with that will be the renaming of |
Will recreate another clean PR once the current open pull request are all merged. Closing. |
This PR changes head extension from
.h
to.hpp
as proposed in #568.Exceptions: ode files and lodepng.h
This pull request includes #652. See this to see only the changes made after #652.