mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: Justin Cormack <justin@specialbusservice.com>
Subject: Re: Squirrel - no-bloat scripting language with sane syntax and semantics
Date: Mon, 26 Aug 2013 17:18:43 -0500	[thread overview]
Message-ID: <1377555523.2737.129@driftwood> (raw)
In-Reply-To: <CAK4o1WyjoX9-aUnvmV+Rqf+Kn4Mrg19Y38pv6zLqVi+ziNhtkA@mail.gmail.com> (from justin@specialbusservice.com on Sun Aug 25 10:03:33 2013)

On 08/25/2013 10:03:33 AM, Justin Cormack wrote:
> On Sun, Aug 25, 2013 at 10:34 AM, Rob Landley <rob@landley.net> wrote:
> > Normally people use lua for this, which has around 100k of  
> interpreter.
> >
> > The downside of lua is it doesn't have a full standard posix C  
> binding
> > library. (It has a nonstandard one you can add on, but when I  
> looked at
> > writing a busybox clone in it, I needed to install something like 7  
> packages
> > to get all the libraries I needed. Then again, most people aren't
> > implementing their own "ifconfig", "mount", and "taskset"...)
> 
> I have implemented ifconfig, mount etc in Lua (the APIs, not the
> commands), see https://github.com/justincormack/ljsyscall - its pretty
> comprehensive now.

While nice, this is another library that's not included in the base lua  
package. A library to implement raw system call bindings, which  
implements support independently for each architecture. A glance at the  
code implies that installing it builds C code somewhere, but after  
finding out that "buildrump.sh" is the name of a subdirectory I stopped  
trying to find where.

The appeal of lua to me was that I _didn't_ have to cross compile C  
stuff, but could instead use a scripting langauge that should just work  
on strange architectures it had never seen before, without cross  
compiling additional packages or installing a native toolchain. (A  
scripting language doesn't even need a build step.)

This library is autogenerating a MK file and probing for CFLAGS. Plus  
raw system calls sans libc wrapping vary slightly between architectures  
anyway, so what this is _trying_ to do wouldn't give me the portability  
I wanted.

Back when I was poking at lua I came to the conclusion I could extend  
lua with C myself, or I could just write my program in C, which is what  
I did.

Rob

  reply	other threads:[~2013-08-26 22:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 21:11 Paul Sokolovsky
2013-08-24  8:29 ` Luca Barbato
2013-08-24 11:29   ` Paul Sokolovsky
2013-08-25  9:34 ` Rob Landley
2013-08-25 15:03   ` Justin Cormack
2013-08-26 22:18     ` Rob Landley [this message]
2013-08-26 23:59       ` Rich Felker
2013-08-27  0:35         ` Rob Landley
2013-08-25 15:18   ` Ivan Kanakarakis
2013-08-25 19:40   ` Paul Sokolovsky
2013-08-25 20:00   ` Matias A. Fonzo
2013-08-25 20:10     ` Rich Felker
2013-08-31 18:39     ` Daniel Cegiełka
2013-09-01 22:43       ` Matias A. Fonzo

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=1377555523.2737.129@driftwood \
    --to=rob@landley.net \
    --cc=justin@specialbusservice.com \
    --cc=musl@lists.openwall.com \
    /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.vuxu.org/mirror/musl/

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).