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: [PATCH olang v1 2/2] docs: spec: add variables and constants specification
Date: Mon, 1 Apr 2024 19:54:02 +0200	[thread overview]
Message-ID: <dc46zge22k5jecm6ky6r2frjpxd6naxbkz7t66f2veyibrq4mz@wf2qyulmlnjq> (raw)
In-Reply-To: <D06OQJQTUJB5.3UK5FGBN4SZDU@maniero.me>

On Fri, Mar 29, 2024 at 10:14:56PM -0300, Carlos Maniero wrote:
> > +<assign-operator>     ::= '='
> > +                        | '*='
> > +                        | '/='
> > +                        | '%='
> > +                        | '+='
> > +                        | '-='
> > +                        | '<<='
> > +                        | '>>='
> > +                        | '&='
> > +                        | '^='
> > +                        | '|='
> I believe we may need two non-terminals, one for assignment which is
> just the '=' and other for reassignments.
> 
> The statements *const x: u32 += 1* is valid in the language but it is
> not valid, but I'm not sure if it also isn't a semantic issue that most
> ignored for the simplicity of the spec. 

Yeah, you are right. But I would love to catch this erro during syntax
analyses. This error looks like a grammatic problem.  What do you think?

> Anyway, since you already addressed most of the issues in the spec I
> propose, few free to send a v2 or let me know what you think about the
> points I raised so then I can proceed with a new version.

I can wait for other revision from you, no problem at all.  Only if you
really want me to do it.

  reply	other threads:[~2024-04-01 16:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  3:21 [PATCH olang v1 0/2] docs: variables specification Carlos Maniero
2024-03-27  3:21 ` [PATCH olang v1 1/2] docs: spec: rename program to translation-unit Carlos Maniero
2024-03-27 21:20   ` Johnny Richard
2024-03-28 13:50     ` Carlos Maniero
2024-03-27  3:21 ` [PATCH olang v1 2/2] docs: spec: add variables and constants specification Carlos Maniero
2024-03-27  3:22   ` [olang/patches/.build.yml] build failed builds.sr.ht
2024-03-27 21:37   ` [PATCH olang v1 2/2] docs: spec: add variables and constants specification Johnny Richard
2024-03-28 14:11     ` Carlos Maniero
2024-04-01 17:48       ` Johnny Richard
2024-03-30  1:14     ` Carlos Maniero
2024-04-01 17:54       ` Johnny Richard [this message]
2024-04-11 22:39     ` [PATCH] fixup! " ricardo_kagawa
2024-04-12 22:36       ` Johnny Richard
2024-04-13  2:18         ` Carlos Maniero
2024-04-16 19:01         ` 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=dc46zge22k5jecm6ky6r2frjpxd6naxbkz7t66f2veyibrq4mz@wf2qyulmlnjq \
    --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