develooper Front page | perl.modules | Postings from September 2001

Re: Rcs::Parser or What namespace should I use?

Thread Previous | Thread Next
From:
Dominique Dumont
Date:
September 27, 2001 16:10
Subject:
Re: Rcs::Parser or What namespace should I use?
Message ID:
kgipu8caeej.fsf@komarr.grenoble.hp.com
andreas.koenig@anima.de (Andreas J. Koenig) writes:

> (CC'd to the RCS experts)
> 
> >>>>> On Wed, 26 Sep 2001 16:49:30 +0200, Ziya Suzen <ziya@ripe.net> said:
> 
> 
>   > The modules I wrote -for my own usage- are:
>   > XXX::Parser           # this the main interface
>   > XXX::YappRcsParser    # produced from a Yapp grammar (Yapp::Parse)
>   > XXX::Deltatext        # impliments RCS deltatext algorithms
> 
>   > Would you please suggest;
> 
>   > 1- Shall I post them to CPAN, do you think others might use it?
> 
> Definitely.
> 
>   > 2- If so, do you think RCS::Parser is a good name to use or not?
> 
> So far the namespaces for RCS are unsatisfying: VCS::RCS, VCS::Rcs,
> and Rcs all exist, maybe it's time to clean that up. Maybe one of the
> RCS experts can chime in and voice an opinion?

OK, so far we have three kinds of modules:
- modules to peek *inside* a VCS system (RCS in this case)
- modules to access VCS systems (VCS::* and VcsTools::*)
- modules to work with and add functionnalities to VCS systems
  (VcsTools::*)

I agree to clean that up. I think everything related to VCS should end
up in VCS::* (or Vcs::*).

Then we'll have to decided whether to split up the namespace for the
various VCS system:

Vcs::Rcs::*
Vcs::Cvs::* 

Then there's the problem of modules than can apply to several vcs
system (like VcsTools::History). 

Should it become Vcs::History, Vcs::Common::History or stay
VcsTools::History ?

What do you think ?

Cheers

-- 
Dominique_Dumont@grenoble.hp.com

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About