mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Squirrel - no-bloat scripting language with sane syntax and semantics
Date: Sat, 24 Aug 2013 14:29:00 +0300	[thread overview]
Message-ID: <20130824142900.3d96356a@x34f> (raw)
In-Reply-To: <52186EE2.8020407@gentoo.org>

Hello,

On Sat, 24 Aug 2013 10:29:22 +0200
Luca Barbato <lu_zero@gentoo.org> wrote:

> > I'd like to draw attention to small very high level (meaning that
> > there's native support for lists and maps) language "Squirrel",
> > http://squirrel-lang.org/ . It compiles below 300K (dynamic linking)
> > with -O2 and can be gotten under 200K with -Os -flto (sizes are for
> > i386). It uses C-like syntax, so should be a quick start for many
> > folks.
> 
> Looks impressively similar to Pawn[1],

Well, depending on how you define "similar". In today's world, one can
say that it's similar to JavaScript, except that it doesn't have all
that "bad parts" which are defining to JS. Overall, there're gazillions
small scripting languages, dead, mature, and unfinished (and over last
half year I looked thru dozens of them). The difference comes to native,
well-integrated support of high-level data types: lists and maps. Very
few support that, and then binary size come into play.

Speaking of Pawn, I see that I looked into it, but I couldn't get its
trunk to compile. And it's advertised as "a compiled language." And
looking thru description, I couldn't find confirmation that it supports
mapping type (appears to be only C-like "structure" with symbolic
identifiers for fixed fields), neither look at source samples confirmed
that, but showed some pretty weird syntax patterns for a "C-like"
language.

All in all, despite difference in syntax, for me Squirrel is similar
to Python (which happens to be my scripting language of choice), and I
treat it exactly like that - unbloated alternative to Python for small
systems.

> with the cons of being written
> in C++ (thus limiting its usage to places where C++ is available),

Squirrel's external API is pure C. It itself implemented in a typical
subset of C++ (-fno-rtti, -fno-exceptions, it does use virtual
destructors though - it's dynamic language implementation after all).

> lua (and moonscript) are getting more and more traction in this field
> and there are lean enough implementations.

Yeah, Lua is definitely (weird) king of the hill here, with networked
package manager avalable, etc. - all like "real" language
(Python/Perl/Ruby). But drawbacks of Lua are well-known - its rather
hacked-up semantics which will make any programmer cringe (conscious
one from dissatisfaction, careless from actual debugging and code
maintenance). I tried to make me not sick of it for about a year and I
failed, hence look for alternative, then understanding that search is
vain and the effort can be rather put into Squirrel (btw, it was
started from dissatisfaction with Lua either).

Here's some comparison of Lua and Squirrel:

http://computerscomputing.wordpress.com/2013/02/18/lua-and-squirrel-the-case-for-squirrel/

> 
> lu
> 
> 
> [1] http://www.compuphase.com/pawn/pawn.htm

-- 
Best regards,
 Paul                          mailto:pmiscml@gmail.com


  reply	other threads:[~2013-08-24 11:29 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 [this message]
2013-08-25  9:34 ` Rob Landley
2013-08-25 15:03   ` Justin Cormack
2013-08-26 22:18     ` Rob Landley
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=20130824142900.3d96356a@x34f \
    --to=pmiscml@gmail.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).