Re: Bring AnyData / DBD::AnyData back to work with modern DBI

Am 13.11.2014 um 17:18 schrieb Jens Rehsack <[email protected]>:

> 
> Am 13.11.2014 um 16:47 schrieb Peter Rabbitson <[email protected]>:
> 
>> On 11/13/2014 04:07 PM, Jens Rehsack wrote:
>>> 
>>> ... "political correctness" guards (sorry, I do not see any advantage in the "don't ever do this because it's forbidden in general").
>> 
>> You need to clarify what you mean, language seems to be getting in the way. What do you perceive as "political correctness", and what do you perceive as "forbidden" ?
> 
> I know that in general an existing (used) API shouldn't be removed without good reason.
> That's why - in particular case - the users of AnyData should say whether they want a fixed AnyData relying on changed API or stick at the current existing darkpan ranks.
> 
> I perceive as "political correctness" you're enforcement of not kicking an existing module (working or not) out of the way in favor of a working successor.


[4:21pm][Sno]: Tux: refresh AnyData ... how proceed ;)
[4:21pm]Tux: hit me
[4:21pm][Sno]: why is "Alt::AnyData::DBITEAM" that bad?
[4:23pm]Tux: would you find that if you were looking for it?
[4:23pm]Tux: DBIx::AnyData ?
[4:25pm][Sno]: Tux: the idea is to have a new module on the one hand without overlaying existing namespace because of hidden incompatibilities
[4:25pm]Tux: so the old one is DBD::AnyData
[4:25pm][Sno]: and being able to use it out-of-the-box with DBI as DBD::AnyData or AnyData as meant with public API
[4:26pm][Sno]: there're 2 modules - AnyData and DBD::AnyData (both old)
[4:26pm]Tux: ahhh (coin drops)
[4:26pm]Tux: Alt::AnyData::DBITEAM is the API?
[4:27pm][Sno]: I "adapted" the name from https://metacpan.org/release/Alt-common-sense-TOBYINK
[4:28pm]Tux: ad*o*pted
[4:28pm][Sno]: point
[4:28pm]Tux: now that I read it, I can accept that name
[4:29pm][Sno]: looks to me as if Toby distributes a new common::sense but doesn't index it
[4:31pm][Sno]: we would distribute an Alt::AnyData::DBITEAM which deploys an AnyData and an DBD::AnyData on with (what should it deploy for co-existence?)
[4:31pm]Tux: no answer
[4:32pm][Sno]: is there a sane way distributing AnyData2/DBD::AnyData2 and on top of that an Alt::AnyData::DBITEAM which adopts the namespaces?
[4:32pm]Tux: .o( kinda fun to see how different minds follow different paths in development )
[4:33pm]Tux: yes, see DDS for Data::Dump::Streamer
[4:33pm]Tux: or DP for Data::Peek
[4:33pm]Tux: you can *ask* the user if installing the (new) names as alias for the better version is ok
[4:44pm]Tux: To expand on that: *my* way would be to implement the two new modules first and rename them into whatever is accepted just before releasing them
[4:44pm]Tux: I want to have fun. name-wars are not fun
[4:46pm][Sno]: Tux: sorry - phone, plumber, ...
[4:47pm][Sno]: I think the option should be there by providing 2nd dist which just overlays for the namespace
[4:47pm][Sno]: maybe ribasushi or timbunce (who both originally voted for new namespace) have an idea regarding that?
[4:49pm][Sno]: but I don't know how an AnyData.pm could look like which just sucks in AnyData2.pm (similar for DBD::AnyData)

Ideas? Comments?

Cheers
-- 
Jens Rehsack
[email protected]