'. '

Search results

From APIDesign

You searched for Backwardcompatibility

Jump to: navigation, search

There is no page titled "Backwardcompatibility".

For more information about searching APIDesign, see Help.

Showing below up to 20 results starting with #1.


View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)

Page title matches

  1. BackwardCompatibility (6,862 bytes)
    1: ...need new upgrades of such downstream libraries. [[BackwardCompatibility]] is the mantra that allows us reach smooth [[Upg...
    5: Does software engineering need [[BackwardCompatibility]]? It is good for anything else than restricting ...
    13: ...o be seen as an advertisement for importance of [[BackwardCompatibility]]. While we keep it, we live in a simple world, a...
    37: ...he end it is the most important one. In case of [[BackwardCompatibility]] we actually do not care that much whether our a...
    43: What could be the best classification of [[BackwardCompatibility]]?

Page text matches

  1. Yet Another Design Book? (1,235 bytes)
    7: ...ver a time, but it is important to do that in a [[BackwardCompatibility|backward compatible]] way - e.g. in a way that no...
  2. The Art of Building Modern Software (2,817 bytes)
    21: ...ng the latest development version. Why? We keep [[BackwardCompatibility]]. Migrating to new version is easy. Still, if th...
  3. LibraryReExportIsNPComplete (12,129 bytes)
    99: If you develop your own libraries in [[BackwardCompatibility|backward compatible]] way, you can always select ...
    107: ...se a library that cannot be trusted to keep its [[BackwardCompatibility]], then do whatever you can to not re-export its ...
    116: ...ete|NP-complete]] problems. Learn to develop in [[BackwardCompatibility|backward compatible]] way. Reading [[TheAPIBook]]...
  4. OlderBlogPosts (111,273 bytes)
    325: ...o. One can deliver improvements while retaining [[BackwardCompatibility]]. All that is needed to teach the [[API]] to acc...
    650: ...obook NP problem] solvers, learn how to achieve [[BackwardCompatibility]].
    704: ==== Just Three Kinds of [[BackwardCompatibility]]? ====
    706: ... finished the online page describing what it is [[BackwardCompatibility]]. It defines three different kinds: source, bina...
  5. Trust (4,434 bytes)
    1: ...the [[APIDesign]]. If you broke your promise of [[BackwardCompatibility]] once, you repel clients of your [[API]] to alte...
    12: Does that mean we need more [[BackwardCompatibility]] in our APIs in order to prevent collapse of sof...
  6. End Of Life Procedures (473 bytes)
    3: ...d APIs to [[black hole]] smoothly while keeping [[BackwardCompatibility]].
  7. SignatureTests (3,631 bytes)
    11: ... has been release in Mar 2009) it supports also [[BackwardCompatibility]] tests. We run the tests daily to ensure that ou...
    40: ... own '''struct'''. Adding new virtual method in [[BackwardCompatibility|backward compatible]] way is almost impossible, a...
    42: Don't get me wrong, I am glad the need for [[BackwardCompatibility]] is realized among [[C]] programmers. Just the s...
  8. Evolving the API Universe (1,068 bytes)
    7: ...also introduces testing style to guarantee full [[BackwardCompatibility]] when rewriting implementation behind existing [...
  9. Blogs:JaroslavTulach:Theory (22,864 bytes)
    62: ... Better to learn and invest in keeping a bit of [[BackwardCompatibility]].
    353: ...|some thoughts]] on the difference between 100% [[BackwardCompatibility]] and their slightly more practical variants.
  10. DistributedDevelopment (684 bytes)
    3: ...f development also heavily relies on concept of [[BackwardCompatibility]]. Only if, things that used to work in previous ...
  11. OSGi (7,935 bytes)
    15: ... compatible - OK, I can understand the value of [[BackwardCompatibility]]. Through at this case it might have been better...
  12. BackwardCompatibility (6,862 bytes)
    1: ...need new upgrades of such downstream libraries. [[BackwardCompatibility]] is the mantra that allows us reach smooth [[Upg...
    5: Does software engineering need [[BackwardCompatibility]]? It is good for anything else than restricting ...
    13: ...o be seen as an advertisement for importance of [[BackwardCompatibility]]. While we keep it, we live in a simple world, a...
    37: ...he end it is the most important one. In case of [[BackwardCompatibility]] we actually do not care that much whether our a...
    43: What could be the best classification of [[BackwardCompatibility]]?
  13. APIFest08:Task2 (1,696 bytes)
    20: ...t 4, 2008. Good luck, and do not forget to keep [[BackwardCompatibility]]!
  14. APIFest08:Task3 (1,779 bytes)
    1: ...implementable'' for you. I guess you all defend [[BackwardCompatibility]] of your solutions pretty well.
  15. APIFest08:Task4 (2,034 bytes)
    2: ...I can tell. Today I spent few hours looking for [[BackwardCompatibility]] problems in provided solutions and I still have...
  16. APIFest08:TaskX (5,452 bytes)
    1: ...n solutions provided by others to find possible [[BackwardCompatibility|evolution]] mistakes. This is a new task, differe...
    3: ...ou can be awarded with '''1 point''' by showing [[BackwardCompatibility|compatibility]] problems in each solution provide...
    44: ...B'' library. If it fails, you have demonstrated [[BackwardCompatibility]] problem and that is why the build succeeds. '''...
  17. Dependencies (5,080 bytes)
    25: ...es the vendor of the library to follow rules of [[BackwardCompatibility]] - e.g. really design and especially [[evolution...
    29: ...veBehaviour]], but sometimes there is really no [[BackwardCompatibility|backward compatible]] way around.
  18. ClientAPI (1,758 bytes)
    5: ...'open space''' which grows with a time. To keep [[BackwardCompatibility]], every method, field or class which has been pr...
    7: ...is a '''final''' class (one cannot cause binary [[BackwardCompatibility]] problems by adding new methods into such class)...
  19. ProviderAPI (3,010 bytes)
    7: ...iders]]. This immediately breaks the promise of [[BackwardCompatibility]].
  20. APIFest08:Report (10,858 bytes)
    7: ... designing architecture and APIs and practising [[BackwardCompatibility]] principles in software interfaces.
    11: ...did not give up and sent me their hacks showing [[BackwardCompatibility]] evolution problems in many solutions.
    15: ...sson to take is that if one is seeking for 100% [[BackwardCompatibility]] one needs to prevent modifications to classes t...
    39: And actually nobody managed to question [[BackwardCompatibility]] of the solution. But '''Jan Žák''' noticed an...
    91: ...ange in [[Runtime Aspects of APIs]] can lead to [[BackwardCompatibility|incompatibilities]].

View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)



Search in namespaces:

List redirects
Search for
Views
Personal tools
buy