Hacker News new | past | comments | ask | show | jobs | submit login

I wish their page included something along the lines of "Why do I care?"

Maybe a few examples of "data munging" tasks which the authors view as poor fits for [language X] and how their stuff solves the problem better.

Maybe something like "why is our language better than regexps in whatever language environment you already know?"




There is page with a navigation frame giving Rosetta Code examples, syntax colored, with back links to Rosetta:

http://www.nongnu.org/txr/rosetta-solutions.html

TXR has regexps is you need them. The regex engine is geared in a different direction from mainstream regex: it doesn't have anchoring, register capture or Perl features like lookbehind assertions. On the other hand it has intersection and negation (without backtracking).

TXR translations of Clojure, Common Lisp and Racket solutions to the same problem:

http://www.nongnu.org/txr/rosetta-solutions-main.html#Self-r...


I saw those; what I miss is "This is why I think this new way is better".

If it's supposed to be obvious by inspection, well... I guess I'm too unenlightened.


I'd say its multi-line approach makes it quite unique when compared to, say, sed or awk.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: