Re: put typedefs in config.h into namespace ost?

[David Sugar]

I believe where we normally choose to come up with these are from their 
absense in the target systems header.  If we are using these convenience 
types internally alone, then they could be moved to private.h, but I think 
external libraries and even some apps now expect these to exist/be defined 
for them in the Common C++ headers...I would have to review that aspect, but 
you may be correct that we could move then into the ost namespace.

On Friday 16 May 2003 07:49 am, Axel Waggershauser wrote:
> Hi,
>
> I have a problem using libcommonc++ together with libtiff, since both
> typedef the same types (int16, int32, etc.). My workaround is to put
> these typedefs in config.h into the namespace ost.
>
> Would it be possible to adopt this fix to the library, so I don't have
> to patch it everytime, or does anybody know of a better solution?
>
> Thanks, Axel.
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp