On Thu, 1 Sep 2016, SF Markus Elfring wrote:
> >> * How much will the data format flexibility evolve together with the
> >> handling
> >> of a key word like "flexible" for metavariables?
> >
> > No idea what this means (data format flexibility).
>
> Is this key word the only one which was added to "PQL" (while it is processed
> by
> "SmPL" in other ways)?
There is an exhaustive list of changes in the paper. To my recollection,
flexible is the only added keyword. In SmPL, it would cause a parse error
in the place where it appears in PQL.
>
>
> >> 3. I get concerns from the section "5.2 Idealized syntax".
> >> How would you categorise it according to the Chomsky-Schützenberger
> >> hierarchy?
> >
> > No idea. It seems like a straightforward BNF.
>
> Does the mentioned syntax belong to the category "context-free"?
I guess, to the extent that any programming language grammar is context
free. Why does it matter?
>
> > The commit range is just X..Y. X ad Y could be commit ids or tags (v4.0,
> > for example).
>
> Can this range be controlled or adjusted from within Prequel scripts anyhow?
No, it is specified on the command line.
>
> >> 5. Can the combination of words like "token" and "regular expression"
> >> be occasionally confusing?
> >
> > Does the word regular expression occur in the paper?
>
> Yes, of course. ;-)
It is used for git. I'm missing what the issue is.
> Is the section "6.1 Commit selection" worth for a few more clarifications?
>
>
> >> 6. How interesting will discussions become around the used hardware
> >> that is mentioned in the chapter "7 Evaluation" and the corresponding
> >> software performance?
> >
> > Not sure what there is to discuss.
>
> Examples:
> * Number of processor cores
1. As is specified in the paper.
>
> * Run time distribution for the involved scripts
>
> >> 7. How is the status for function and class libraries for this application
> >> domain?
> >
> > No idea what this means.
>
> Would you like to share any more information around the evolving code design
> structure?
> Which class libraries will eventually combine software modules?
I don't even know what a class library is in this context.
>
>
> How do you think about to use another public repository interface
> which would be similar to the one for Coccinelle?
I tried github, but the indices don't fit due to github file size
limitations. Since I ignore all of the features of github other than the
basic git features, I don't care. I believe that gforge has a bug
tracker, but I would have to figure out how to enable it.
julia
_______________________________________________
Cocci mailing list
[email protected]
https://systeme.lip6.fr/mailman/listinfo/cocci
