in reply to Re^3: Basic regex to parse source code
in thread Basic regex to parse source code
I think my post as more harsh than I intended. I like contrasting solutions that display how a certain problem would be solved easier or even different in another language. But that requires that the poster highlights and explains the differences and how the differences are crucial, instead of posting a "solution" without any explanation.
For example, I have code that loops over cartesian products of arrays to find out the sets of elements that fulfill certain criteria. In the context of posts about that code, a solution in Prolog would certainly be shorter and exhibit far more beauty than nested loop constructs do in Perl. So, mentioning Prolog there, potentially with the example translated to Prolog would be OK.
As another example, changing the SQL statement from fetching all rows and then doing calculations in Perl to doing most of the calculation in the database already is another case where another language than Perl is discussed (and hopefully used).
But I didn't find any such discussion, or even beauty/succinctness/differentness in the posts by JennyC.
|
|---|