public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: Carlos Maniero <carlos@maniero.me>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Carlos Maniero <carlos@maniero.me>
Subject: [PATCH olang v3 0/2] spec: parser: enable expression on function level
Date: Thu, 10 Oct 2024 16:29:28 +0000 (UTC)	[thread overview]
Message-ID: <20241010162918.338338-1-carlos@maniero.me> (raw)

v3:
- transform the assignment expression into a binop
- fix unary precedence

Carlos Maniero (2):
  spec: parser: enable expression on function level
  parser: fix unary precedence

 docs/info/specification.texi      | 18 ++++++-------
 src/ast.c                         | 14 ----------
 src/ast.h                         |  2 +-
 src/checker.c                     |  8 ------
 src/codegen_linux_x86_64.c        | 35 ++++++++++++++-----------
 src/lexer.c                       |  1 +
 src/parser.c                      | 43 +++++--------------------------
 src/pretty_print_ast.c            | 40 ++++++++++++++++------------
 tests/olc/0029_var_assigment.ol   |  2 +-
 tests/olc/0030_while_statement.ol |  2 +-
 tests/olc/0034_pointers.ol        | 43 +++++++++++++++++++++++++++++++
 11 files changed, 107 insertions(+), 101 deletions(-)
 create mode 100644 tests/olc/0034_pointers.ol


base-commit: d45df92d81f00059ecd1f6478bac7e4511d9fd8d
-- 
2.46.1


             reply	other threads:[~2024-10-10 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 16:29 Carlos Maniero [this message]
2024-10-10 16:29 ` [PATCH olang v3 1/2] " Carlos Maniero
2024-10-10 16:29 ` [PATCH olang v3 2/2] parser: fix unary precedence Carlos Maniero
2024-10-10 16:30   ` [olang/patches/.build.yml] build success builds.sr.ht
2024-10-11  0:32 ` [PATCH olang v3 0/2] spec: parser: enable expression on function level Johnny Richard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241010162918.338338-1-carlos@maniero.me \
    --to=carlos@maniero.me \
    --cc=~johnnyrichard/olang-devel@lists.sr.ht \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.johnnyrichard.com/olang.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox