| Revision | 74d7bf9944d15bcdbff22d67f434af6d04094afc (tree) |
|---|---|
| Zeit | 2016-10-23 23:03:20 |
| Autor | OCTAGRAM <bo_ <gen@octa...> |
| Commiter | OCTAGRAM <bo_ |
Note about incremental text editing
| @@ -12,8 +12,8 @@ | ||
| 12 | 12 | |
| 13 | 13 | ## Amount of information ## |
| 14 | 14 | |
| 15 | -* Emitter Framework: Limited by what is reachable from processed IDL and included ones. Unresolved forward class declarations are possible. For instance, ::SOMClassMgr::somInterfaceRepository method returns ::Repository object reference, but somcm.idl does not include repostry.idl. | |
| 16 | -* Interface Repository Framework: Contains information gathered from multiple IDLs in one place. No unresolved forward class declarations allowed. | |
| 15 | +* Emitter Framework: Limited by what is reachable from processed IDL and included ones. Unresolved forward class declarations are possible. For instance, ::SOMClassMgr::somInterfaceRepository method returns ::Repository object reference, but somcm.idl does not include repostry.idl. Emitters like "imod" collecting information from several IDLs at once have to incrementally edit output file. They put signatures into text file to locate where to append new strings. Incremental updates of text files is hard to implement in more complex cases. | |
| 16 | +* Interface Repository Framework: Contains information gathered from multiple IDLs in one place. No unresolved forward declarations allowed. | |
| 17 | 17 | |
| 18 | 18 | ## Information precision ## |
| 19 | 19 |
Fork
Emitter Framework vs. Interface Repository Framework.md