Good evening,
Martin Wilke a écrit :
> |> In order to continue this, I'm thinking of using uint32_t instead of
> |> Uint32 in include/action.{cpp,h}. However, this is C99, and I'm not
> |sure > all environments (*BSD) have it included as automatically as
> |for gnu > systems.
> |
> |C++ has been d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 15 Jul 2007 18:21:16 +0200
Matthieu Fertré <[EMAIL PROTECTED]> wrote:
|Kurosu a écrit :
|> Kurosu a écrit :
|>
|>> I've spent some time "cleaning" the includes by using forward
|>> declarations. This means that not all headers are automatic
Kurosu a écrit :
> Kurosu a écrit :
>
>> I've spent some time "cleaning" the includes by using forward
>> declarations. This means that not all headers are automatically
>>
>
> In order to continue this, I'm thinking of using uint32_t instead of
> Uint32 in include/action.{cpp,h}. However,
Kurosu a écrit :
> I've spent some time "cleaning" the includes by using forward
> declarations. This means that not all headers are automatically
In order to continue this, I'm thinking of using uint32_t instead of
Uint32 in include/action.{cpp,h}. However, this is C99, and I'm not sure
all envir
Hi!
> I've spent some time "cleaning" the includes by using forward
> declarations. This means that not all headers are automatically
> included, and that the .cpp should include the appropriate header if it
> ever uses (by allocation/destruction or use of a method) something known
> through a for
