Namespacing Collection

[Nikolaj Hald Nielsen]

MusicCollection is a bad name IMO as it might have nothing to do with
music ( audio books, podcasts... )

how about putting it in the Meta namespace? ( I ams sure someone has a
thousand reason why that is a really bad idea... )

- Nikolaj

On Sun, Dec 7, 2008 at 7:06 PM, Leo Franchi <lfranchi at kde.org> wrote:
> hey guys,
>
> i'm in the process of adding Growl support for os x (growl is the
> standardized notification system for os x, think the OSD on steroids),
> and as this is a os x class, it requires the Carbon.h header (os x
> headers). anyway, Carbon.h contains a typedef Collection, non-
> namespaced, that conflicts with our own Collection.
>
> do people have technical problems with me namespacing the Collection
> stuff into its own namespace? i'm thinking Amarok::, but don't really
> know what the best name would be.
>
> another options is renaming Collection itself to e.g. MusicCollection.
>
> thoughts?
>
> leo
>
> ---
> Leo Franchi                             (650) 704 3680
> Tufts University 2010
>
> lfranchi at kde.org
> leonardo.franchi at tufts.edu
>
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>