转换前缀表示法给出的表达式,识别公共子表达式和依赖关系
我在 ANSI 文本文件中得到了一堆前缀表示法的表达式。我想生成另一个 ANSI 文本文件,其中包含这些表达式的逐步评估。例如:
- + ^ x 2 ^ y 2 1
应该变成
t1 = x^2
t2 = y^2
t3 = t1 + t2
t4 = t3 - 1
t4 is the result
我还必须识别常见的子表达式。例如,
expression_1: z = ^ x 2
expression_2: - + z ^ y 2 1
expression_3: - z y
我必须生成一个输出,说明 x 出现在表达式 1、2 和 3(通过 z)中。
我必须确定依赖项:表达式_1 仅依赖于 x,表达式_2 依赖于 x 和 y 等。
原始问题比上面的示例更困难,我无法控制输入格式,它采用前缀表示法方法比上面的复杂。
我已经在 C++ 中实现了一个有效的实现,但是在 C++ 中执行此类操作非常痛苦。
什么编程语言最适合解决这些类型的问题?
你能推荐一个我可以开始的教程/网站/书籍吗?
我应该寻找哪些关键词?
更新:根据答案,上面的例子有点不幸,我的输入中有一元、二元和n元运算符。 (如果您想知道,exp 是一元运算符,范围内的 sum 是 n 元运算符。)
I am given a bunch of expressions in prefix notation in an ANSI text file. I would like to produce another ANSI text file containing the step-by-step evaluation of these expressions. For example:
- + ^ x 2 ^ y 2 1
should be turned into
t1 = x^2
t2 = y^2
t3 = t1 + t2
t4 = t3 - 1
t4 is the result
I also have to identify common subexpressions. For example given
expression_1: z = ^ x 2
expression_2: - + z ^ y 2 1
expression_3: - z y
I have to generate an output saying that x appears in expressions 1, 2 and 3 (through z).
I have to identify dependecies: expression_1 depends only on x, expression_2 depends on x and y, etc.
The original problem is more difficult than the examples above and I have no control over the input format, it is in prefix notation in a much more complicated way than the above ones.
I already have a working implementation in C++ however it is a lot of pain doing such things in C++.
What programming language is best suited for these type problems?
Could you recommend a tutorial / website / book where I could start?
What keywords should I look for?
UPDATE: Based on the answers, the above examples are somewhat unfortunate, I have unary, binary and n-ary operators in the input. (If you are wondering, exp
is an unary operator, sum
over a range is an n-ary operator.)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(7)
为了让您了解这在 Python 中是什么样子,这里有一些示例代码:
输出与示例输出相同。
除了这个例子之外,我认为您列出的任何高级语言几乎同样适合该任务。
To give you an idea how this would look like in Python, here is some example code:
The output is the same as your example output.
This example aside, I think any of the high-level languages you listed are almost equally suited for the task.
sympy
python 包进行符号代数运算,包括公共子表达式消除和为一组表达式生成求值步骤。请参阅:http://docs.sympy.org/dev/modules/rewriting.html (查看页面底部的
cse
方法)。The
sympy
python package does symbolic algebra, including common subexpression elimination and generating evaluation steps for a set of expressions.See: http://docs.sympy.org/dev/modules/rewriting.html (Look at the
cse
method at the bottom of the page).Python 示例非常简短,但我怀疑您实际上无法通过这种方式对表达式进行足够的控制。您最好实际构建一个表达式树,尽管这需要更多工作,然后查询该树。下面是 Scala 中的一个示例(适合剪切并粘贴到 REPL 中):
这可能有点难以一次性消化,但话又说回来,这确实有很多作用。
首先,它是完全防弹的(请注意大量使用
Option
,结果可能会失败)。如果你向它扔垃圾,它只会返回None
。 (多做一点工作,你可以让它以一种信息丰富的方式抱怨这个问题——基本上是case Op(o)
,然后嵌套两次parseParts
可以代替存储结果并在操作未获取两个参数时打印出信息丰富的错误消息。同样,parse
可能会抱怨尾随值,而不是仅仅返回None
。)其次,当你完成它后,你就拥有了一个完整的表达式树。请注意,
printTemp
打印出您想要的临时变量,varsUsed
列出了特定表达式中使用的变量,一旦解析多个表达式,您就可以使用它来扩展为完整列表。线。 (如果您的变量不仅仅是a
到z
,您可能需要稍微修改一下正则表达式。)另请注意,表达式树以正常中缀形式打印出来符号。让我们看一些示例:现在,您可以在 Python 中完成此操作,而无需太多额外的工作,此外还可以在许多其他语言中完成此操作。我更喜欢使用 Scala,但您可能更喜欢其他方式。无论如何,如果您想保留处理棘手情况的最大灵活性,我确实建议您创建完整的表达式树。
The Python example is elegantly short, but I suspect that you won't actually get enough control over your expressions that way. You're much better off actually building an expression tree, even though it takes more work, and then querying the tree. Here's an example in Scala (suitable for cutting and pasting into the REPL):
This may be a little much to digest all at once, but then again, this does rather a lot.
Firstly, it's completely bulletproof (note the heavy use of
Option
where a result might fail). If you throw garbage at it, it will just returnNone
. (With a bit more work, you could make it complain about the problem in an informative way--basically thecase Op(o)
which then doesparseParts
nested twice could instead store the results and print out an informative error message if the op didn't get two arguments. Likewise,parse
could complain about trailing values instead of just throwing backNone
.)Secondly, when you're done with it, you have a complete expression tree. Note that
printTemp
prints out the temporary variables you wanted, andvarsUsed
lists the variables used in a particular expression, which you can use to expand to a full list once you parse multiple lines. (You might need to fiddle with the regexp a little if your variables can be more than justa
toz
.) Note also that the expression tree prints itself out in normal infix notation. Let's look at some examples:Now, you could do this in Python also without too much additional work, and in a number of the other languages besides. I prefer to use Scala, but you may prefer otherwise. Regardless, I do recommend creating the full expression tree if you want to retain maximum flexibility for handling tricky cases.
使用普通递归解析器来实现前缀表示法非常简单。例如:
这将生成如下输出:
这可以轻松扩展。例如,要处理多个表达式语句,您可以使用:
Yielding:
Prefix notation is really simple to do with plain recursive parsers. For instance:
This will generate output like this:
This can be easily expanded. For instance, to handle multiple expression statements you can use this:
Yielding:
好吧,既然递归解析器不是你的菜,这里有一个解析组合器的替代方案:
这就是你得到的结果:
n-Ary 运算符
Ok, since recursive parsers are not your thing, here's an alternative with parse combinators:
This is the kind of results you get:
n-Ary operator
事实证明,这种解析对我来说也很感兴趣,所以我在这方面做了更多的工作。
似乎有一种感觉,像简化表达这样的事情很难。我不太确定。让我们看一下一个相当完整的解决方案。 (
tn
表达式的打印对我来说没有用,而且您已经有几个 Scala 示例,所以我将跳过它。)首先,我们需要提取语言的各个部分。我将选择正则表达式,尽管也可以使用解析器组合器:
非常简单。我们定义可能出现的各种事物。 (我决定用户定义的变量只能是单个小写字母,并且数字可以是浮点型,因为您有
exp
函数。)r
最后意味着这是一个正则表达式,它会给我们括号中的内容。现在我们需要代表我们的树。有多种方法可以做到这一点,但我将选择一个具有特定表达式的抽象基类作为案例类,因为这使得模式匹配变得容易。此外,我们可能想要良好的打印效果,因此我们将重写
toString
。不过,大多数情况下,我们将使用递归函数来完成繁重的工作。大多数情况下,这是相当乏味的——每个案例类都会覆盖基类,并且
text
和args
自动填充def
。请注意,我已经确定list
是一个可能的 n 元函数,并且它将与行号一起打印出来。 (原因是,如果有多行输入,有时将它们作为一个表达式一起使用会更方便;这使它们成为一个函数。)定义数据结构后,我们需要解析表达式。将要解析的内容表示为标记列表很方便;当我们解析时,我们将返回一个表达式和我们尚未解析的剩余标记——这对于递归解析来说是一个特别有用的结构。当然,我们可能无法解析任何内容,因此最好也将其包装在
Option
中。请注意,我们使用模式匹配和递归来完成大部分繁重的工作——我们选取列表的一部分,计算出我们需要多少个参数,然后递归地传递这些参数。 N 元操作有点不太友好,但我们创建了一个小递归函数,它会为我们一次解析 N 个东西,并将结果存储在缓冲区中。
当然,这使用起来有点不友好,所以我们添加了一些包装函数,让我们可以很好地与之交互:
好吧,现在,简化一下怎么样?我们可能想做的一件事是数值简化,我们预先计算表达式并用其简化版本替换原始表达式。这听起来像是某种递归操作——找到数字,然后将它们组合起来。首先,我们使用一些辅助函数来对数字进行计算:
然后我们进行简化:
再次注意,大量使用模式匹配来查找何时处于良好的情况,并调度适当的计算。
现在,代数代换肯定要困难得多!实际上,您需要做的就是注意到已经使用了一个表达式,并分配一个变量。由于我上面定义的语法允许就地变量替换,因此我们实际上可以修改表达式树以包含更多变量赋值。所以我们这样做(编辑为仅在用户没有插入变量的情况下插入变量):
就是这样 - 一个功能齐全的代数替换例程。请注意,它构建了所看到的表达式集,并特别跟踪哪些表达式是重复的。感谢案例类的魔力,所有的等式都为我们定义好了,所以它可以正常工作。然后我们可以在递归查找重复项时替换它们。请注意,替换例程被分成两半,并且它匹配树的未替换版本,但使用替换版本。
好的,现在让我们添加一些测试:
它是如何做的?
所以我不知道这对你是否有用,但事实证明对我有用。这是我在 C++ 中非常犹豫是否要解决的问题,因为许多原本应该很容易的事情最终却变得很痛苦。
编辑:这是一个使用此结构打印临时分配的示例,只是为了证明此结构完全可以完成此类操作。
代码:
选定的结果(来自
listAssignments(useTempVars(r)).foreach(printf(" %s\n",_))
):第二次编辑:查找依赖项也不错。
代码:
如果我们添加新的测试用例
val test7 = "list 3 z = ^ x 2 - + z ^ y 2 1 w = - z y"
和val test8 = "list 2 x = yy = x"
并使用for ((v,d) <- listDependents(r)) println(" "+v+" require "+d)
显示答案,我们得到(选定的结果):所以我认为,在这种结构之上,您所有的个人需求都可以通过一两打 Scala 代码块来满足。
编辑:这里是表达式求值,如果您给出从变量到值的映射:
并且在测试例程中像这样使用它:
给出如下结果(输入
x = 3
和y = 1.5
):另一个挑战——挑选出尚未使用的变量——只是从依赖项
结果
列表中设置减法。diff
是集合减法方法的名称。It turns out that this sort of parsing is of interest to me also, so I've done a bit more work on it.
There seems to be a sentiment that things like simplification of expressions is hard. I'm not so sure. Let's take a look at a fairly complete solution. (The printing out of
tn
expressions is not useful for me, and you've got several Scala examples already, so I'll skip that.)First, we need to extract the various parts of the language. I'll pick regular expressions, though parser combinators could be used also:
Pretty straightforward. We define the various things that might appear. (I've decided that user-defined variables can only be a single lowercase letter, and that numbers can be floating-point since you have the
exp
function.) Ther
at the end means this is a regular expression, and it will give us the stuff in parentheses.Now we need to represent our tree. There are a number of ways to do this, but I'll choose an abstract base class with specific expressions as case classes, since this makes pattern matching easy. Furthermore, we might want nice printing, so we'll override
toString
. Mostly, though, we'll use recursive functions to do the heavy lifting.Mostly this is pretty dull--each case class overrides the base class, and the
text
andargs
automatically fill in for thedef
. Note that I've decided that alist
is a possible n-ary function, and that it will be printed out with line numbers. (The reason is that if you have multiple lines of input, it's sometimes more convenient to work with them all together as one expression; this lets them be one function.)Once our data structures are defined, we need to parse the expressions. It's convenient to represent the stuff to parse as a list of tokens; as we parse, we'll return both an expression and the remaining tokens that we haven't parsed--this is a particularly useful structure for recursive parsing. Of course, we might fail to parse anything, so it had better be wrapped in an
Option
also.Note that we use pattern matching and recursion to do most of the heavy lifting--we pick off part of the list, figure out how many arguments we need, and pass those along recursively. The N-ary operation is a little less friendly, but we create a little recursive function that will parse N things at a time for us, storing the results in a buffer.
Of course, this is a little unfriendly to use, so we add some wrapper functions that let us interface with it nicely:
Okay, now, what about simplification? One thing we might want to do is numeric simplification, where we precompute the expressions and replace the original expression with the reduced version thereof. That sounds like some sort of a recursive operation--find numbers, and combine them. First we get some helper functions to do calculations on numbers:
and then we do the simplification:
Notice again the heavy use of pattern matching to find when we're in a good case, and to dispatch the appropriate calculation.
Now, surely algebraic substitution is much more difficult! Actually, all you need to do is notice that an expression has already been used, and assign a variable. Since the syntax I've defined above allows in-place variable substitution, we can actually just modify our expression tree to include more variable assignments. So we do (edited to only insert variables if the user hasn't):
That's it--a fully functional algebraic replacement routine. Note that it builds up sets of expressions that it's seen, keeping special track of which ones are duplicates. Thanks to the magic of case classes, all the equalities are defined for us, so it just works. Then we can replace any duplicates as we recurse through to find them. Note that the replace routine is split in half, and that it matches on an unreplaced version of the tree, but uses a replaced version.
Okay, now let's add a few tests:
How does it do?
So I don't know if that's useful for you, but it turns out to be useful for me. And this is the sort of thing that I would be very hesitant to tackle in C++ because various things that were supposed to be easy ended up being painful instead.
Edit: Here's an example of using this structure to print temporary assignments, just to demonstrate that this structure is perfectly okay for doing such things.
Code:
Selected results (from
listAssignments(useTempVars(r)).foreach(printf(" %s\n",_))
):Second edit: finding dependencies is also not too bad.
Code:
And if we add new test cases
val test7 = "list 3 z = ^ x 2 - + z ^ y 2 1 w = - z y"
andval test8 = "list 2 x = y y = x"
and show the answers withfor ((v,d) <- listDependents(r)) println(" "+v+" requires "+d)
we get (selected results):So I think that on top of this sort of structure, all of your individual requirements are met by blocks of one or two dozen lines of Scala code.
Edit: here's expression evaluation, if you're given a mapping from vars to values:
and it's used like so in the testing routine:
giving results like these (with input of
x = 3
andy = 1.5
):The other challenge--picking out the vars that haven't already been used--is just set subtraction off of the dependencies
result
list.diff
is the name of the set subtraction method.该问题由两个子问题组成:解析和符号操作。在我看来,答案可以归结为两种可能的解决方案。
一是从头开始实现一切:“如果您想保留处理棘手情况的最大灵活性,我确实建议您创建完整的表达式树。” - 由雷克斯提出。正如 Sven 指出的那样:“您列出的任何高级语言几乎同样适合该任务”,但是“Python(或您列出的任何高级语言)不会消除问题的复杂性。 ”
我收到了非常好的 Scala 解决方案(非常感谢 Rex 和 Daniel),这是一个很好的 Python 小示例(来自 Sven)。然而,我仍然对 Lisp、Haskell 或 Erlang 解决方案感兴趣。
另一种解决方案是使用一些现有的库/软件来完成任务,并具有所有隐含的优点和缺点。候选者是 Maxima (Common Lisp)、SymPy (Python,由 payne 提出) 和 GiNaC (C++)。
The problem consists of two subproblems: parsing and symbolic manipulation. It seems to me the answer boils down to two possible solutions.
One is to implement everything from scratch: "I do recommend creating the full expression tree if you want to retain maximum flexibility for handling tricky cases." - proposed by Rex. As Sven points out: "any of the high-level languages you listed are almost equally suited for the task," however "Python (or any of the high-level languages you listed) won't take away the complexity of the problem."
I have received very nice solutions in Scala (many thanks for Rex and Daniel), a nice little example in Python (from Sven). However, I am still interested in Lisp, Haskell or Erlang solutions.
The other solution is to use some existing library/software for the task, with all the implied pros and cons. Candidates are Maxima (Common Lisp), SymPy (Python, proposed by payne) and GiNaC (C++).