hi there,

i'm working on a module to interface with music player daemon (mpd).
i've released:
 - audio::mpd, a traditional oo interface
 - poe::component::client::mpd, a poe-aware interface

they're both under development.

for each of them, i've defined an item class to map the items
manipulated by mpd. there are 3 subclasses item::song,
item::directory and item::playlist.

note that:
 - those items are just a bunch of accessors,
 - those items do not retrieve their information themselves from a file
   or whatever

my problem is that those classes are defined both:
 - in audio::mpd::item (with audio::mpd::item::* subclasses)
 - and poe::component::client::mpd::item (with pococm::item::*
   subclasses)

and the code is the same, with only the package name differing.

since code duplication is bad, and since i don't want to put a prereq
relationship between the 2 modules (in either direction), i'm going to
extract the item::* classes in their own module that's going to be
prereq by the others.

i haven't seen any such thing on cpan, it's always tied to a format
(mp3, or ogg vorbis, or...) and meant to extract meta-information from a
file.

so here's my question: how should i name this new module?
 - audio::item    => isn't it too vague?
 - audio::mpditem => isn't it too specific? (would it be used by others?)
 - other?


thanks for your help,
jérôme 
-- 
[EMAIL PROTECTED]

Reply via email to