Skip to main content
Mathematica

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    $\begingroup$ That's incredible! Thanks for keeping up a great work, this is very useful for all of us, much appreciated. $\endgroup$ Commented Sep 17, 2013 at 13:42
  • $\begingroup$ You're welcome, you're the hero of many of these posts. $\endgroup$ Commented Sep 17, 2013 at 14:52
  • 1
    $\begingroup$ @Leonid I've collected some of your answers where you use a parsing approach, if there are other such posts could you please add them to the list ? $\endgroup$ Commented Jan 18, 2014 at 22:30
  • 2
    $\begingroup$ Thanks. It's good that this technique is now systematically represented here, I think it is an important one. I have added this one, and my answer for the code formatter question (since in a sense formatter is also an expression parser, and in fact a pretty sophisticated one), which are the only ones that comes to mind right now. $\endgroup$ Commented Jan 19, 2014 at 12:56
  • 2
    $\begingroup$ I find the most difficult part of Mathematica is controlling evaluation (because there isn't just a single way to do it), and I think it's very important for the future of Mathematica, where macros (or code for rewriting code) is the horizon. The post above is extremely valuable. $\endgroup$ Commented Dec 27, 2014 at 12:26