From 3448e2aa81a01244458824aae94d3e746a9a4c24 Mon Sep 17 00:00:00 2001 From: Hans Bolinder Date: Sat, 5 Jan 2013 09:26:34 +0100 Subject: Fix some FOP warnings Examples overflowing the width of PDF pages have been fixed. The remaining warnings are due to table cells, and require more work. --- lib/orber/doc/src/ch_idl_to_erlang_mapping.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'lib/orber/doc/src') diff --git a/lib/orber/doc/src/ch_idl_to_erlang_mapping.xml b/lib/orber/doc/src/ch_idl_to_erlang_mapping.xml index 964ae3e92d..1fd2f644cb 100644 --- a/lib/orber/doc/src/ch_idl_to_erlang_mapping.xml +++ b/lib/orber/doc/src/ch_idl_to_erlang_mapping.xml @@ -4,7 +4,7 @@
- 19972010 + 19972013 Ericsson AB. All Rights Reserved. @@ -1142,7 +1142,8 @@ handle_info(_Info, State) -> module, and lookup in DB_Administrator_impl.erlandDB_CommonUser_impl.erl. But wait, is that really necessary? Actually, it is not. We simple use the IC compile option impl:

-$ erlc +'{{impl, "DB::CommonUser"}, "DBUser_impl"}'  +'{{impl, "DB::Administrator"}, "DBUser_impl"}' DB.idl
+$ erlc +'{{impl, "DB::CommonUser"}, "DBUser_impl"}'\
+ +'{{impl, "DB::Administrator"}, "DBUser_impl"}' DB.idl
 $ erlc *.erl
     

Instead of creating, and not the least, maintaining two call-back modules, -- cgit v1.2.3