objective c - Is Cocotron the result of reverse engineering? -
Is it to repeat the behavior of different libraries (hence the call is exactly the same) optimization and new ways to do their stuff Are you
In the Room and Clean Room Dirty rooms basically know some ways to disassemble the machine code What this does is and is using the disambeld code to create a new code. The dirty room creates the problem of copyright infringement, you are basically stealing the old system to create new systems directly or indirectly through the direct knowledge of the old system implementation. Including documentation and testing against the system to implement the same API in a clean room. These two techniques can be used in self or different combinations. For example, PC Bios was a reverse engineer using two teams, a dirty-room team, which separated the original BIOS and created a specification and a clean-room team that implemented the new BIOS using the specification. High bets for reverse engineering Typical situations usually include attorneys specializing in the field so that they can create appropriate new implementation, which does not violate the old one.
Cocotron is a clean-room implementation I / We use documentation and testing programs to create a new implementation (coktrron) that matches the behavior of the old implementation (cocoa). Apple documentation is very good, APIs are well organized and it is easy to create a test program when necessary. Cocotron is great if I say this, but of course it is not cocoa and I imagine that the sources are very different between the two.
Comments
Post a Comment