|
Geometry : |
Subject: [ggl] Header inclusion guards
From: Mateusz Loskot (mateusz)
Date: 2009-04-17 07:40:25
Barend Gehrels wrote:
>> However, thinking of Boost'ification, I'm not sure, but we may need
>> to change it again.
>>
>> Layout of Boost libraries is as follows:
>> - headers
>> <root>/boost/<lib>/
>> - translation units, tests, examples, doc
>> <root>/libs/<lib>/test
>> <root>/libs/<lib>/example
>> <root>/libs/<lib>/doc
>> <root>/libs/<lib>/...
>
> Sure, I realized that making the last preview and creating the boost
> sandbox. We should change that. This change will need to adapt all
> project files and header files and maybe more. But it is necessary.
Yes and I'm willing to apply or help in applying relevant changes.
> Let's plan a date for this.
As I imagine this is related to the schedule of issuing previews,
I'd leave the planning to you and Bruno :-)
>> Given that, if we agree to re-structure ggl, then inclusion guards will
>> look exactly as you are suggesting:
>>
>> GGL_STRATEGIES_DISTANCE_RESULT_HPP
>> GGL_GEOMETRIES_...
>> etc.
>
> OK, so at least that is right then.
That's right.
>> Perhaps it seems a cosmetic, but I wouldn't be sure if it is.
>> Many of Boost conventions have been already applied to GGL,
>> so why not to apply Boost structure too, especially if GGL
>> is going to be merged into Boost one day.
>
> Sure. The name GGL is adapted last february, that is why all headerfiles
> refer to geometry/ (in fact the name ggl was very old also but then
> stood for Geodan Geographic Library)
Got it.
Best regards,
-- Mateusz Loskot, http://mateusz.loskot.net
Geometry list run by mateusz at loskot.net