Sure.  The component's own .h is first, followed by a blank line.


----- Original Message -----
From: reply@reply.github.com
To: bsl@noreply.github.com
Cc: JOHN LAKOS (BLOOMBERG/ 731 LEXIN)
At: Feb 16 2013 23:43:05



In groups/bsl/bslstl/bslstl_string.t.cpp:
> @@ -1,7 +1,6 @@
>  // bslstl_string.t.cpp                                                -*-C++-*-
>  
>  #include <bslstl_string.h>
> -

If we stick by the strict letter of the BDE C++ Standards Guide, it says 


Include directives must be divided into 3 groups:
a) components in the same package as this component

b) components from other packages

c) other required headers that are not components (e.g. third-party or platform-specific)



I'm taking this to mean there should be no extra space after the component include.   Stylistically I can see having the extra space after the component '.h' include and having it clarifies to what needs to be alphabetized.   

            
              —
              Reply to this email directly or 
view it on GitHub.
            
            {https://github.com/notifications/beacon/8p9wzwlzvt2eivdu4muotule-bb55io9wh8ysbo5_mbk7mtroilugoo905lfk8px.gif}