Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I guess there's marginal semantic value in discriminating between vector and eigenvector in regards to intent. But on the whole, yeah, pick a single library if they do the same thing.
-
Looks like you need to wrap the actually needed functionality of all that libs and do all the type-casting at the abstraction border.
Then you can always use the same vector implementation in the code wich is using the wrappers... -
@hasu
Well, research code normally has the following life cycle:
It gets made. Then it gets improved until it is fit for its purpose (normally a paper or degree). Then it is abandoned and never gets touched again.
Maybe, you actually plan on maintaining it later. But the myriads of rotten research projects out in the wild are overwhelming evidence for such a future being highly unlikely.
So skip the todo list. Get it good enough, turn it into publication score or a degree and move on to the next project to repeat the cycle...
Related Rants
My Unreal project right now:
FVector
std::vector
Eigen::Vector
KDL::Vector
....
*sigh*
And people ask me why I like Lisp. A Vector is a Vector goddamit! Half my project is now just parsing the same variable to the different functions. sigh....I hate this.
rant
unreal engine
parsing struggles
third party libraries