9front - general discussion about 9front
 help / color / mirror / Atom feed
From: raingloom <raingloom@riseup.net>
To: 9front@9front.org
Subject: Re: [9front] lua9: lua interpreter with plan9 bindings
Date: Wed, 28 Oct 2020 21:47:06 +0100	[thread overview]
Message-ID: <20201028214706.32ed9f21@riseup.net> (raw)
In-Reply-To: <1EB1CC8CE0933B539E5C6F5317FCD7EE@gmail.com>

On Tue, 27 Oct 2020 11:41:38 +0100
telephil9@gmail.com wrote:

> > On Tue, Oct 27, 2020 at 9:20 AM <telephil9@gmail.com> wrote:  
> >>
> >> Hi,
> >>
> >> Building on the lua port by staalmannen
> >> (http://github.com/staalmannen/lua), I wrote a custom version of
> >> the lua interpreter including bindings to some plan9 libraries. I
> >> feel that lua is a simple (and good enough) scripting language
> >> which makes writing GUI code more convenient than in C. For the
> >> time being, this includes bindings for libdraw but I plan to
> >> extend this to other plan9 libraries in the future (libplumb for
> >> instance). 
> > 
> > Nice work!
> > I imagine you wrote a custom interpreter because Plan 9 does not
> > have a well established dynamic library mechanism. Do you plan on
> > embedding everything into the interpreter?  
> 
> Thanks.
> 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.
> 

Do you plan on porting it from APE to native Plan 9 libaries?
That would allow native code to link to liblua.a.

I have a WIP port that does that, but I have other projects that need
my attention more.

Personally, I'd love to use Lua instead of Acid's rather limited
scripting language, that's my biggest motivation for writing the port.


  reply	other threads:[~2020-10-28 22:49 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 [this message]
2020-10-29  6:33       ` telephil9
2020-10-29 11:38         ` Iruatã Souza
2020-10-29 12:09     ` Ethan Gardener
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=20201028214706.32ed9f21@riseup.net \
    --to=raingloom@riseup.net \
    --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).