Issue 6064 - Put C++ code into a configurable namespace

compiled/base.h

 /*
  * This file is part of Adblock Plus <https://adblockplus.org/>,
  * Copyright (C) 2006-present eyeo GmbH
  *
  * Adblock Plus is free software: you can redistribute it and/or modify
  * it under the terms of the GNU General Public License version 3 as
  * published by the Free Software Foundation.
  *
  * Adblock Plus is distributed in the hope that it will be useful,
  * but WITHOUT ANY WARRANTY; without even the implied warranty of
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  * GNU General Public License for more details.
  *
  * You should have received a copy of the GNU General Public License
  * along with Adblock Plus. If not, see <http://www.gnu.org/licenses/>.
  */
 
 #pragma once
 
 // if a user config is not specified then use the default location.
 #if !defined(ABP_USER_CONFIG)
-#  define ABP_USER_CONFIG "user.h"

[hub, 2017/11/21 16:48:39]

I would call this "user-config.h". and the present header config.h instead of
base.h.

We could also consider having it generated from the build system.

But this is just my suggestion.

Also I would just have the content of "user.h" here if ABP_USER_CONFIG is
undefined.

[sergei, 2017/11/22 09:39:26]

I like to have config.h with a more specific part user-config.h which is also
close to ABP_USER_CONFIG. I actually thought about config/user.h and just
omitted 'config' for the sake of simplicity.
I have renamed user.h to user-config.h.

What concerns base.h, I considered it as not only a place for configuration. For
instance base.h could also include some additional very common headers or have
some project specific defines. So, when we need it in my opinion we should not
go again through all relevant files and change config.h to some base.h.
Therefore I would propose to have
base.h
  include config.h
    include user-config.h
but currently having both config.h and base.h seems redundant, so I would
propose to not complicate it for present, it will be very easy to add config.h
when it's really needed. What do you think about it?
The idea is that one can simply copy user-config.h and adjust few parameters, if
it is inlined then one will have to firstly figure out what should be in a
custom user-config.h. So, IMO it should not be inlined.

+#  define ABP_USER_CONFIG "user-config.h"
 #endif
 // it should be the first included file
 #ifdef ABP_USER_CONFIG
 #include ABP_USER_CONFIG
 #endif