>> Do you find the documentation complete for this functionality at the moment? > > No idea.
How can we achieve a better common understanding on this aspect for example? >> I imagine a need for advanced configuration possibilities around “regexp” >> engines. > > You imagine many things. Yes, of course. ;-) > Changes will only happen when there is a concrete need. I came along some development needs also together with software experiments around SmPL scripts. How do your needs look different over time? >> Is the current approach the official one already? > > Yes. Thanks for this information. >>> Perhaps the constraint scrpt syntax could be generalized to allow more >>> in practice than function calls. >> >> Which software development concerns can hinder progress in the way >> I imagine so far? > > Lack of time. > >> >>> That might happen some day, but it is an extremely low priority. >> >> I am curious if the involved dependencies can be clarified further. > > I doubt there are any dependencies. Our software development capacity is limited as usual. Will future software research activities improve the situation a bit more? >> https://github.com/coccinelle/coccinelle/blob/cbc751b30d9e02390d60ebed643c8e4a3fa0bb2b/tests/idcon_ocaml.cocci > > In the test case the braces are around a function call, not a function name. This detail is also clear for me to some degree. > No idea what could be relevant or irrelevant about it. I got further ideas for this software area after a delay. > That is the syntax that has been implemented. I wonder still why such a variant was chosen. > It may change when someone when someone motivated enough to work on the > implementation writes the code to make the change and tests the result. My motivation could eventually increase if the understanding of the corresponding OCaml source code could become better somehow besides other factors. > It won't change just because someone finds it conceptually inelegant > and sends lots of emails about it. So there is some usual change resistance. I dare to provide intensive feedback in the hope that details can be uncovered which can support more progress. > It's actually strange that you want to define regexps in other places, This detail is just another aspect for the involved software evolution. > but you don't want to define scripts in other places. I got also further ideas around the placement of script fragments. > Why not just define a python function that you can call in a script > to do your big regexp for you? This approach can only work safely if script constraints will be completely documented in the manual (besides one test case in OCaml and Python). Regards, Markus _______________________________________________ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
