Andy Armstrong <a...@hexten.net> writes: > On 11 Feb 2009, at 12:38, Andy Armstrong wrote: >>> There are no TAPx:: modules there except the intermediate >>> TAPx::Parser >>> which is now TAP::Parser. But there are some TAP:: modules. That's >>> why >>> I ask. >> >> >> I'd say TAP::Data is absolutely fine. > > > But, of course, Ovid is right about ::Data being a bit generic :)
Maybe I explain it in more detail, so we can think about (the|a better) name. Initially I want to query TAP against Data::DPath expressions. For this purpose I need a reliable data structure that containes parsed TAP. Once stable, this structure will practically never change, it acts like an API for other libs that evaluate on TAP. Like I do with Data::DPath. Internally my module "TAP::Data" is just a call of TAP::Parser and collecting all data into this data structure. Summary: The only purpose of this module is a) to define a *reliable* data structure definition and b) help create it from TAP. I once thought it might also fit into TAP::Convert::* but I plan to also optionally "type" the data structure, so that such data might also become "ref eq 'TAP::Data'" at some time, e.g. for Moose'ish programs. There the "::Convert" would not work. Kind regards, Steffen -- Steffen Schwigon <s...@renormalist.net> Dresden Perl Mongers <http://dresden-pm.org/> German Perl-Workshop 2009 <http://www.perl-workshop.de/en/2009>
