Changes between Version 2 and Version 3 of Ticket #424
- Timestamp:
- 2013-03-13T10:33:41Z (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #424 – Description
v2 v3 10 10 The IPC in HelenOS is mostly asynchronous and thus the concept of calls and callbacks is necessary. However, the implementation shall not provide only the naive implementation of classical callbacks but also the concept of futures (promises) to allow writing the servers in the same pseudo-synchronous manner as it is today. 11 11 [[br]][[br]] 12 In the first iteration, the IDL can support only basic types (plain integers and blocks of memory would be sufficient for majority of the interfaces), features such as structures or arrays .12 In the first iteration, the IDL can support only basic types (plain integers and blocks of memory would be sufficient for majority of the interfaces), features such as structures or arrays can be added later. 13 13 [[br]][[br]] 14 14 The result of the compilation (generation) would be a set of C sources and headers files containing: … … 25 25 26 26 What Gains and Benefits will this bring?:: 27 There should be no impact at all to the functionality of HelenOS as an operating system. The benefit would be in making the code more readable because a lot of similar code would be removed, being replaced by an automatically generated one. The presence of such generator would also simplify greatly adding ofnew interfaces. In the longer term, it would simplify creating bindings for other languages (e.g. OOP-style generator for C++).27 There should be no impact at all to the functionality of HelenOS as an operating system. The benefit would be in making the code more readable because a lot of similar code would be removed, being replaced by an automatically generated one. The presence of such generator would also simplify the process of adding a new interfaces. In the longer term, it would simplify creating bindings for other languages (e.g. OOP-style generator for C++). 28 28 29 29 Difficulty::
