public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: Johnny Richard <johnny@johnnyrichard.com>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Johnny Richard <johnny@johnnyrichard.com>
Subject: [PATCH olang v1 0/3] add support to compile extern fn def
Date: Thu, 17 Oct 2024 04:04:41 +0200	[thread overview]
Message-ID: <20241017020603.551431-1-johnny@johnnyrichard.com> (raw)

Johnny Richard (3):
  lexer: spec: add extern keyword for function def
  parser: support extern function definition
  codegen: x64: compile extern function definition

 docs/info/olang.ebnf                |  2 +-
 src/ast.c                           |  3 ++-
 src/ast.h                           |  2 ++
 src/checker.c                       |  4 ++-
 src/codegen_x86_64.c                |  4 +++
 src/lexer.c                         |  5 ++++
 src/lexer.h                         |  1 +
 src/parser.c                        | 20 ++++++++++++---
 src/pretty_print_ast.c              | 14 +++++++----
 tests/olc/0037_variable_overflow.ol | 39 +++++++++++++++++++++++++++++
 10 files changed, 83 insertions(+), 11 deletions(-)
 create mode 100644 tests/olc/0037_variable_overflow.ol


base-commit: 160969fc5bd259f1fa2dacd2ba85e366d3b8f5d0
-- 
2.46.0


             reply	other threads:[~2024-10-17  0:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  2:04 Johnny Richard [this message]
2024-10-17  0:11 ` Carlos Maniero
2024-10-17  2:04 ` [PATCH olang v1 1/3] lexer: spec: add extern keyword for function def Johnny Richard
2024-10-17  0:07   ` [olang/patches/.build.yml] build success builds.sr.ht
2024-10-17  2:04 ` [PATCH olang v1 2/3] parser: support extern function definition Johnny Richard
2024-10-17  2:04 ` [PATCH olang v1 3/3] codegen: x64: compile " 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=20241017020603.551431-1-johnny@johnnyrichard.com \
    --to=johnny@johnnyrichard.com \
    --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