From: Johnny Richard <johnny@johnnyrichard.com>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Johnny Richard <johnny@johnnyrichard.com>
Subject: [PATCH olang v1 2/3] lexer: add tilde token support
Date: Wed, 9 Oct 2024 23:18:28 +0200 [thread overview]
Message-ID: <20241009213425.412949-3-johnny@johnnyrichard.com> (raw)
In-Reply-To: <20241009213425.412949-1-johnny@johnnyrichard.com>
The tilde token will be used for parsing bitwise-not unary operator.
Signed-off-by: Johnny Richard <johnny@johnnyrichard.com>
---
src/lexer.c | 6 +++++
src/lexer.h | 1 +
tests/olc/0033_unary_operator_bitwise_not.ol | 27 ++++++++++++++++++++
3 files changed, 34 insertions(+)
create mode 100644 tests/olc/0033_unary_operator_bitwise_not.ol
diff --git a/src/lexer.c b/src/lexer.c
index 5b4bbaa..9e012bd 100644
--- a/src/lexer.c
+++ b/src/lexer.c
@@ -258,6 +258,11 @@ lexer_next_token(lexer_t *lexer, token_t *token)
lexer_skip_char(lexer);
return;
}
+ case '~': {
+ lexer_init_char_value_token(lexer, token, TOKEN_TILDE);
+ lexer_skip_char(lexer);
+ return;
+ }
case '/': {
lexer_init_char_value_token(lexer, token, TOKEN_SLASH);
lexer_skip_char(lexer);
@@ -303,6 +308,7 @@ static char *token_kind_str_table[] = {
[TOKEN_DASH] = "-",
[TOKEN_STAR] = "*",
[TOKEN_SLASH] = "/",
+ [TOKEN_TILDE] = "~",
[TOKEN_EQ] = "=",
[TOKEN_CMP_EQ] = "==",
[TOKEN_BANG] = "!",
diff --git a/src/lexer.h b/src/lexer.h
index 8beaea8..774f619 100644
--- a/src/lexer.h
+++ b/src/lexer.h
@@ -81,6 +81,7 @@ typedef enum token_kind
TOKEN_DASH,
TOKEN_SLASH,
TOKEN_STAR,
+ TOKEN_TILDE,
TOKEN_LF,
TOKEN_OPAREN,
TOKEN_CPAREN,
diff --git a/tests/olc/0033_unary_operator_bitwise_not.ol b/tests/olc/0033_unary_operator_bitwise_not.ol
new file mode 100644
index 0000000..1891549
--- /dev/null
+++ b/tests/olc/0033_unary_operator_bitwise_not.ol
@@ -0,0 +1,27 @@
+# Copyright (C) 2024 olang mantainers
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <https://www.gnu.org/licenses/>.
+
+fn main(): u32 {
+ var e: u32 = 4294967295
+ return ~e
+}
+
+# XTEST test_compile(exit_code=0)
+#
+# XTEST test_run_binary(exit_code=0)
+#
+# TEST test_contains_tokens WITH
+# ./0033_unary_operator_bitwise_not.ol:18:10: <~>
+# END
--
2.46.0
next prev parent reply other threads:[~2024-10-09 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 21:18 [PATCH olang v1 0/3] implement unary operator for bitwise not Johnny Richard
2024-10-09 21:18 ` [PATCH olang v1 1/3] doc: add unary expression to language spec Johnny Richard
2024-10-09 21:18 ` Johnny Richard [this message]
2024-10-09 21:18 ` [PATCH olang v1 3/3] parser: codegen(x86_64): add bitwise not unary op support Johnny Richard
2024-10-09 19:35 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-10-09 23:00 ` [PATCH olang v1 0/3] implement unary operator for bitwise not Carlos Maniero
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=20241009213425.412949-3-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