From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] lua9: lua interpreter with plan9 bindings
Date: Thu, 29 Oct 2020 12:09:09 +0000 [thread overview]
Message-ID: <b3b6112e-abc5-4c3e-a23f-ed30c65eb447@www.fastmail.com> (raw)
In-Reply-To: <1EB1CC8CE0933B539E5C6F5317FCD7EE@gmail.com>
On Tue, Oct 27, 2020, at 10:41 AM, telephil9@gmail.com wrote:
>
> Yes, the lack of dynamic library loading gives no other choice than
> embedding everything in the interpreter.
> This is the reason why I wrote this instead of lua modules as you would
> find on other platforms.
I once considered implementing libraries in the interpreted language, (Forth in my case,) interacting with the files in /dev, but I realized a big C binary is better. Plan 9 only loads the parts of the binary which are needed, so there's no disadvantage to a big binary. If I remember right, it also shares the text segment when you load multiple instances, saving memory.
next prev parent reply other threads:[~2020-10-29 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 8:20 telephil9
2020-10-27 10:34 ` [9front] " Iruatã Souza
2020-10-27 10:41 ` telephil9
2020-10-28 20:47 ` raingloom
2020-10-29 6:33 ` telephil9
2020-10-29 11:38 ` Iruatã Souza
2020-10-29 12:09 ` Ethan Gardener [this message]
2020-10-28 11:06 ` Ethan Gardener
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=b3b6112e-abc5-4c3e-a23f-ed30c65eb447@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).