On 04/17/11 21:29, Adriano dos Santos Fernandes wrote:
> Unfortunately my proposal can't be done.
>
> There is the forward decls that can't be declared in another namespace.
>
> There is a second option. There is nothing much "namespace Jrd" opening,
> so is possible to change all of them.
>
> But
Unfortunately my proposal can't be done.
There is the forward decls that can't be declared in another namespace.
There is a second option. There is nothing much "namespace Jrd" opening,
so is possible to change all of them.
But there is a lot of Jrd::, specially in _proto.h files. I never
unders
12.04.2011 2:09, Adriano dos Santos Fernandes wrote:
> I suggest we fix namespace usages in an incremental manner. How?
>
> [skip]
>
> This way subsystems are children of Firebird namespace and don't require
> "Firebird::" everywhere. We also avoid "using namespace Firebird" in
> implementation fi
On 11-04-2011 20:23, Claudio Valderrama C. wrote:
>> -Original Message-
>> From: Adriano dos Santos Fernandes [mailto:adrian...@gmail.com]
>> Sent: Lunes, 11 de Abril de 2011 18:10
>>
>> Usage of namespaces in our code is very ugly, as we divide things in
>> main-level namespaces.
>>
>> In
> -Original Message-
> From: Adriano dos Santos Fernandes [mailto:adrian...@gmail.com]
> Sent: Lunes, 11 de Abril de 2011 18:10
>
> Usage of namespaces in our code is very ugly, as we divide things in
> main-level namespaces.
>
> In headers, we have lot of "Firebird::". They're specially
All,
Usage of namespaces in our code is very ugly, as we divide things in
main-level namespaces.
In headers, we have lot of "Firebird::". They're specially ugly in this
type of usage:
Firebird::Pair > >
With make almost "obligatory" to create extra typedefs.
I suggest we fix namespace usages in