Namespace hierarchies

[Jeff Mitchell]

On 3/29/2010 3:10 PM, Bart Cerneels wrote:
> 1) grouped by implementation backend:
> ex. for Sql
> Sql::Collecion
> Sql::Meta::Track
> Sql::Playlist
> Sql::Podcast::Episode

This doesn't provide for any real organization. What is "Sql"? What is
the "Sql" interface?

> 2) or by core namespace:
> Collections::SqlCollection
> Meta::Sql::Track
> Playlists::Sql::Playlist
> Podcasts::Sql::Episode

This makes it much more clear -- you have the core interface, then the
implementation backend, then the class.

> I think 1) is superior because it saves massively on typing (ex):
> 
> using namespace Sql:::Podcast;

Um...

using namespace Podcasts::Sql;

...am I missing something here?

--Jeff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/amarok-devel/attachments/20100329/e7fbf387/attachment.sig