Lutz Schönemann wrote:
> But is there a documentation about IDL4? Something that tells me what
> files are created and what exactly IDL4 does?
IDL4 is, from what I got so far, a subset of the CORBA IDL, which
defines interfaces between servers and clients. This IDL is used by
an IDL compiler ("magpie") to generate the server and the client
skeleton and stub code, respectively. This code does nothing else
than piping your calls through OKL4 IPCs. In addition, you get handed
the server loop function, which waits for incoming calls and deploys
them to the respective "business" code.
All in all, up to 3 files are generated (at least in OKL4 2.1):
Two files (one .h and one .c) for the server side (declarations and
the server loop code), and one file (.h) for the client side. I dunno
about the server side files; the client side include file is only
generated if it's actually used somewhere (i.e. by having an
#include <interfaces/...> in your client code).
The IDL provides a couple "annotations" to interfaces, enclosed in
brackets "[....]", like an uuid() to differ between interfaces if
multiple have been specified, or the presence of an async or
exception handler.
A thing which seemingly doesn't work is defining data structures
(maybe someone can correct me on that one); you will have to use
#include-s of header files if you want to other than the default
data types.
Robert
_______________________________________________
Developer mailing list
[hidden email]
https://lists.okl4.org/mailman/listinfo/developer