public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: "Carlos Maniero" <carlos@maniero.me>
To: "Carlos Maniero" <carlos@maniero.me>,
	"Johnny Richard" <johnny@johnnyrichard.com>
Cc: <~johnnyrichard/olang-devel@lists.sr.ht>
Subject: Re: [RFC] Namespaces in OLANG
Date: Sun, 07 Apr 2024 23:45:18 -0300	[thread overview]
Message-ID: <D0EEAMTCOP41.1M075M3G9GR55@maniero.me> (raw)
In-Reply-To: <D0E6XB0HJ8ET.1QG9HPVR5LEES@maniero.me>

Johnny and I have been discussing this subject outside of this thread and it
seems we weren’t able to make much progress due to certain communication
anti-patterns.

Initially, I was attempting to address multiple issues simultaneously:

- Name collision
- Import resolution
- Namespaces
- External linking
- Assembly symbol generation

Even though these subjects are interconnected, it might be more effective to
discuss each one individually.

Additionally, I realized that I was somewhat attached to the solution I had
designed during my first attempt at creating a programming language (Mars).
This may not necessarily be the most suitable solution for our current
situation.

We are still trying to learn how to properly communicate over email. Given
these considerations, I believe it would be beneficial to start a new thread
where we can address these issues individually.

      reply	other threads:[~2024-04-08  2:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24  2:46 Carlos Maniero
2024-03-27 18:39 ` Johnny Richard
2024-03-28 13:41   ` Carlos Maniero
2024-04-06 16:51     ` Johnny Richard
2024-04-07 20:49       ` Carlos Maniero
2024-04-07 20:58         ` Carlos Maniero
2024-04-08  2:45           ` Carlos Maniero [this message]

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=D0EEAMTCOP41.1M075M3G9GR55@maniero.me \
    --to=carlos@maniero.me \
    --cc=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