Changes between Version 1 and Version 2 of Ticket #259, comment 3
- Timestamp:
- Jul 10, 2017, 3:31:39 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #259, comment 3
v1 v2 3 3 ABI changes other than adding a completely new function almost always mean changing function signatures. For C++ it is done automatically in most cases. For plain C it's the author's responsibility to rename the function if it's signature changes. And if the function is renamed, the automatic dependency generator will catch it. 4 4 5 Regarding the dependency tree. While I think that RPMDB is capable of handling thousands of dependencies, I agree that C++ imposes some problems (I already wrote about that). But given that the OS/2 kernel itself feels pretty much ok with them, I guess RPM will also do. And as a last resort, If we are not satisfied with real-life tests, we may simply disable this generator for C++ symbols.5 Regarding the dependency tree. While I think that RPMDB is capable of handling thousands of dependencies, I agree that C++ may theoretically impose some problems (I already wrote about that and I thought exactly about AOO and also about Qt). But given that the OS/2 kernel itself feels pretty much ok with them, I guess RPM will also do. And as a last resort, If we are not satisfied with real-life tests, we may simply disable this generator for C++ symbols. 6 6 7 7 So I still think we should do it.