public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: Johnny Richard <johnny@johnnyrichard.com>
To: Carlos Maniero <carlos@maniero.me>
Cc: ~johnnyrichard/olang-devel@lists.sr.ht
Subject: Re: [RFC SPEC] Primitive data types and arrays
Date: Sun, 14 Apr 2024 01:31:42 +0200	[thread overview]
Message-ID: <ijnnessvkbk3npn7gqhlolfm3mrw43b2feq6ryffqt7qi7jfw2@dc5fw4jhgyzy> (raw)
In-Reply-To: <D0INKDECJMDD.3EPYTTM3HJZNO@maniero.me>

On Fri, Apr 12, 2024 at 11:51:51PM -0300, Carlos Maniero wrote:
> > I loved it.  Out of curiosity, we are going to have _boolean_ and _char_
> > I believe.  Shouldn't they also be included on these primitive spec?
> 
> I like it! We could discuss in the near feature if they are or not just
> type alias for u8. But I also agree they must be built-in without the
> need of any include.
> 
> <primitive-type>      ::= 's8'| 's16'| 's32'| 's64'| 'u8'|
>                           'u16'| 'u32'| 'u64'| 'f32'| 'f64'|
>                           'char' | 'bool'
> <expression>          ::= <integer> | <identifier> | <boolean> | <char>
> <boolean>             ::= "true" | "false"
> <char>                ::= "'" #'.' "'" 

Perhaps _char_ SHOULD have support to escaped chars like \r (carried
return), \n (line feed)...  Whenever you create the patch, don't forget it.

> Are you comfortable with the above grammar?

I am wondering if we should also define _void_ as a primitive.

  reply	other threads:[~2024-04-13 22:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08  3:29 Carlos Maniero
2024-04-12  7:32 ` Johnny Richard
2024-04-13  2:51   ` Carlos Maniero
2024-04-13 23:31     ` Johnny Richard [this message]
2024-04-16  3:40       ` Carlos Maniero
2024-04-16 18:34         ` Johnny Richard
2024-04-17  1:30           ` ricardo_kagawa
2024-04-18 21:53             ` Carlos Maniero
2024-04-24 16:23               ` ricardo_kagawa
2024-04-20 11:45             ` Johnny Richard
2024-04-24 18:45               ` ricardo_kagawa

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=ijnnessvkbk3npn7gqhlolfm3mrw43b2feq6ryffqt7qi7jfw2@dc5fw4jhgyzy \
    --to=johnny@johnnyrichard.com \
    --cc=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