Hi Jürgen,
here's a little fix. The base64 chars had S and T misplaced.
Tobia
--- src/QuadFunction.cc(revision 520)
+++ src/QuadFunction.cc(working copy)
@@ -413,8 +413,8 @@
const ShapeItem full_quantums = B.element_count() / 3;
const ShapeItem len_Z = 4 *
Hi Tobia,
the quick answer is this. Suppose we have:
A / ¨ B.
The the parser does this:
read B (no pattern match)
read ¨ (no pattern match)
read /
At this point we could:
(i) take / to mean (function) comp
Thanks.
I understand that there is a tradeoff involving run-time lookahead. It's
still not entirely clear to me why simple cases would parse correctly, even
with a user-defined symbol as the left argument (A/B) while applying an
operator would break the parser (A/¨B). I'll have to study the parser
