SineSwiper

(11:18:06 AM) SineSwiper: some interesting stuff: http://eli.thegreenplace.net/2010/01/02/top-down-operator-precedence-parsing/
(11:20:42 AM) SineSwiper: especially this: http://eli.thegreenplace.net/2009/03/20/a-recursive-descent-parser-with-an-infix-expression-evaluator/
(11:20:56 AM) SineSwiper: this is exactly the problem I'm having with a_expr and the like
(11:21:45 AM) SineSwiper: and I was close to what the solution was supposed to be: descending levels of recursion
(11:23:17 AM) SineSwiper: ingy: ^^^
(11:34:24 AM) SineSwiper: it's looking like Pegex should be supporting some form of %left/%right syntax

(9:47:03 PM) SineSwiper: ingy: the more I'm converting this, the more I'm thinking there should be a { } syntax in Pegex that introduces an Acmeist "return language"
(9:48:37 PM) SineSwiper: the tree needs to be warped into place, and it's annoying that simple changes like "opt_nowait:   NOWAIT { TRUE }" end up having to be split into two files
(9:48:41 PM) rking: SineSwiper: What do you mean by “"retu

SineSwiper

#############################################################################
#
#      QUERY:
#            DEALLOCATE [PREPARE] <plan_name>
#
#############################################################################
DeallocateStmt  : DEALLOCATE PREPARE? (
     name { @->[0] }
   | ALL  { NULL   }
) {

SineSwiper

sunday_morning: Im waking up | ( cant even focus on a coffee_cup )
coffee_cup: dont even know whos bed Im in

# Parser problems
lyric:
   where
   do
   I
   start
where

SineSwiper

# "Atoms"
E_CODE : /(
   <C_LCURLY>
   (:
      [^ <C_LCURLY><C_RCURLY> ]+ |  # Most stuff
      (?1)                          # Nesting braces
   )*
   <C_RCURLY>
)/
E_PERCODE  : / <PERCENT><E_CODE> ~ /  # bit of a hack, as it swallows the % from %}\n