> > From: Geoff Rowell [mailto:geoff.rowell_at_gmail.com]
> > Sent: 22 April 2010 14:21
> > To: Giulio Troccoli
> > Cc: users_at_subversion.apache.org
> > Subject: RE: Common name for transaction and revision object
> >
> > Giulio Troccoli <Giulio.Troccoli_at_uk.linedata.com> wrote:
> > >
> > > I'm writing the hooks for a new repository in Perl and I'm
> > exploring
> > > using
> > OO Perl. In both pre- and post-commit hooks I need the list
> > of files, the author and other similar information. My idea
> > was to define a class and create an instance of that class
> > given either the transaction number adn repository path or
> > the revision number and the repository URL. The 'new'
> > function will then initialise all the information I need
> > calling either svnlook or svn. For instance:
> > >
> > > my $transaction = new Transaction($txn, $repo_path);
> > >
> > > Or
> > >
> > > my $commit = new Commit($rev, $repo_url);
> > >
> > > As you can see they are almost the same, so it would be
> > nice to have a
> > single class (I could then check the second parameter to see
> > if it's a URL or a path and do things accordingly). But I
> > cannot come up with a single name that would encompass both,
> > and that's what I'm asking the list.
> > >
> > > So, any suggestions?
> >
>
> Sorry, for posting again but I haven't received any
> suggestions regarding the name. Nobody can come up with
> anything? Really?
>
> G
>
What about "Transaction" or "BaseTransaction" or "TransactionBase"? A
commit is just a specific transaction anyway.
What does the other poster use in the framework he pointed you to?
~ mark c
Received on 2010-04-28 16:01:38 CEST