From ed62e11f0ec629858ab927bc79dc85bab2419614 Mon Sep 17 00:00:00 2001 From: schmidt Date: Mon, 14 Jun 2004 19:02:50 +0000 Subject: ChangeLogTag:Mon Jun 14 13:58:02 2004 Douglas C. Schmidt --- docs/ACE-guidelines.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'docs') diff --git a/docs/ACE-guidelines.html b/docs/ACE-guidelines.html index ab140cc92c3..0b56983ba2e 100644 --- a/docs/ACE-guidelines.html +++ b/docs/ACE-guidelines.html @@ -302,7 +302,7 @@ The correct way to write that guard is: // Put your template declarations here... #if defined (__ACE_INLINE__) - #include "Foo_T.i" + #include "Foo_T.inl" #endif /* __ACE_INLINE__ */ #if defined (ACE_TEMPLATES_REQUIRE_SOURCE) @@ -333,7 +333,7 @@ The correct way to write that guard is: #endif /* ACE_LACKS_PRAGMA_ONCE */ #if !defined (__ACE_INLINE__) - #include "ace/Foo_T.i" + #include "ace/Foo_T.inl" #endif /* __ACE_INLINE__ */ ACE_RCSID(lib, Foo_T, "$Id$") @@ -359,7 +359,7 @@ The correct way to write that guard is: // Put your non-template declarations here... #if defined (__ACE_INLINE__) - #include "Foo.i" + #include "Foo.inl" #endif /* __ACE_INLINE__ */ #include "Foo_T.h" @@ -468,7 +468,7 @@ The correct way to write that guard is:
  • Avoid unnecessary parenthesis. We're not writing Lisp :-)

    -

  • Put inline member functions in a .i +
  • Put inline member functions in a .inl file. That file is conditionally included by both the .h file, for example:

    @@ -479,7 +479,7 @@ The correct way to write that guard is: }; #if defined (__ACE_INLINE__) - #include "ace/High_Res_Timer.i" + #include "ace/High_Res_Timer.inl" #endif /* __ACE_INLINE__ */

    @@ -490,7 +490,7 @@ The correct way to write that guard is: #include "ace/High_Res_Timer.h" #if !defined (__ACE_INLINE__) - #include "ace/High_Res_Timer.i" + #include "ace/High_Res_Timer.inl" #endif /* __ACE_INLINE__ */ ACE_ALLOC_HOOK_DEFINE(ACE_High_Res_Timer) @@ -498,7 +498,7 @@ The correct way to write that guard is: NOTE: It is very important to ensure than an inline function will not be used before its definition is seen. - Therefore, the inline functions in the .i file should be arranged + Therefore, the inline functions in the .inl file should be arranged properly. Some compilers, such as g++ with the -Wall option, will issue warnings for violations.

    -- cgit v1.2.1