msramalho / feup-comp Goto Github PK

Class that workers should return that provides a simple way of extracting and combining their results

Figure out a way of passing the operation to execute into the respective worker factory so that PatternReport knows which operation to execute: sum, count, avg, ... list even...

In such a way that the operations on the PatternReport can be extended by users

this was actually fixed by Spoon in CtScanner

• use SnippetCompilationHelper
• CtCodeSnippet cenas
• associate with first node (to trigger worker call)

on Dispatcher's run: spoon.getModel().getAllPackages() -> chamar recursivamente em cada class do package (pode ser paralelo) -> método dentro do dispatcher que usa a threadPool dele

Something that reads the name of the method in this line

isto não funciona:

 @Override
    protected AbstractFilter setFilter() {
        CtIterator iterator = new CtIterator(patternElement);
        //TODO: get the first valid element from the CtBlock -> this approach does not work
        if (iterator.hasNext() && iterator.next() != null && iterator.hasNext()) return new TypeFilter(iterator.next().getClass());
        return null;
    }

é preciso uma forma de obter o primeiro elemento que vai dizer onde é que se despoleta o worker

• Think of this so that it is good for cmd and Java package
• Extract the calculations of the worker factories in use from the run() method
• isolate the values the Dispatcher needs from the configuration (for example number of threads)

passar collection de operators ao PatternReport,
no Report .toString chamar operate dos vários pattern reports associados à String Operator.getName

name do operator é passado no construtor, criado na factory dos respectivos workers, factory chama worker.getName, estáticos têm nome associado, e dinâmicos vão buscar o nome do método

FactoryManager getWorkerFactory should return list of Factories and not just the first one, see the line here

• Depends on #7
• Make Main(String args[]) accept the Patterns.java class
• Iterate over the Patterns.java when creating WorkerFactories

• Isolate WorkerFactory into WorkerFactoryInterface
• SpoonWorkerFactory implements WFI (essentially what we have)
• PatternWorkerFactory implements WFI (receives CtElement for the pattern)

the implementation was done at the beginning and was not returning a WorkerReport, like so:

return new WorkerReport(<RES>);

Develop incrementally:

• just for _var_x() in the beginning
• include _any_() functionality
• include _any_(from, to) functionality

Steps for this:

• isolate logic that interprets a method as _var_X() or _any_
• architecture to receive the source CtElement and the pattern CtELement
• Create "symbol table" for the variables. If it has not been seen -> add, if it has -> check match
• Use flag to "stop consuming" when _any_() is found
• Implement a lazy matcher, but with backtrack

Desired behaviour

CtIterator iterator = new CtIterator(/** some CtElement*/); 
while (iterator.hasNext()) { 
    CtElement next = (CtElement) iterator.next(); 
    logger.print(next.toString()); 
}

http://spoon.gforge.inria.fr/mvnsites/spoon-core/apidocs/spoon/template/TemplateMatcher.html

Assess usefulness of this class, probably does our work for us...