I'd suggest this:
- Frederico, tell us where you think we should introduce an interface so that you could plugin a new LOC algorithm. This is likely to require an injection mechanism and removing lots of static calls, probably home-made if we do not want any dependency (Guice / Spring, spring would d be OTT)
- I think we should improve the caching mechanism to store the results of more than 1 algorithm (each algo would have its own name 'loc' being the basic one we have.
- may be allow more than 1 algorithm collecting the data at the same time? That way we could keep LOC but also some other algo... But we'd need to think how is the model built (based on StatCVS) and whether we should improve it to have a 'type' for the stats... Or simply launch say statsvn with a given loc mode...
What do you think? Food for thoughts...
B
------------------------------
IMPORTANT NOTICE
This communication contains information that is considered confidential and may also be privileged . It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender and delete the original.
-----Original Message-----
From: Maggi Federico <
[hidden email]>
Date: Sun, 15 Mar 2009 21:58:25
To: <
[hidden email]>
Subject: Re: [Statsvn-developers] Counting LOC matching a regexp
Jason,
thanks for your quick reply.
On Mar 15, 2009, at 9:20 PM, Jason Kealey wrote:
> If you wanted to take StatSVN and change the meaning of a LOC (to
> match that regexp), then I think it should be fairly easy to change
> the locations that do look the line counting.
>
> Take a look at statsvn\src\net\sf\statsvn\util\SvnDiffUtils, the
> parseDiff function.
This is a good news, I'll play with it a bit.
> For your research project, it should be fairly easy to perform these
> line counts. During your testing, keep in mind that StatSVN keeps a
> LOC cache.
I know this is a lame question but, may I avoid this? If not, what's
the recommended way to clean that cache?
> However, if you ever want to contribute something back to StatSVN in
> terms of something that would be reusable for the masses, that's
> another story (a lot more complex).
Researcher's life is a valley of deadlines, but I promise I will do it
if will have time.
Thanks! Best regards,
-- Federico
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial.
http://p.sf.net/sfu/www-adobe-com_______________________________________________
Statsvn-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/statsvn-developers------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial.
http://p.sf.net/sfu/www-adobe-com_______________________________________________
Statsvn-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/statsvn-developers