public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sg@belvok.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] kernel+shell: tclsh
Date: Fri, 02 Jun 2006 14:22:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.63.0606021714120.27131@sg.belavox.gomel.by> (raw)

Hello

I'd read a polemic about a redboot+kernel+shell behavior. I often use
tclsh for my own needs and think why do not use it? John Ousterhout
originally created Tcl as exactly an embeddable extension language. A
bit googling net I found 'The Jim Interpreter' (http://jim.berlios.de).
The Jim is the Tcl8.5 based cut (hack) for small footprint systems. It
is an open source project. In 5 minutes I compiled jim for my LPC2294
target (2M RAM) with -DJIM_ANSIC -Os flags (I used the `default' ecos
template with a `posix' package). I'd got a binary image about ~180k
(the lpc2294 has 256k on-chip flash memory). After a burning the image
I'd got a well know shell (well, I changed the Jim default prompt :).

% info commands
subst list ref time debug test eval env lrange setref lappend proc break
llength return linsert error catch split info rand collect if join
concat lambda source global switch getref for lreverse append format
finalize lmap package set lambdaFinalizer scan while * + dict - uplevel
continue / rename foreach lset tailcall upvar unset expr load exit
lindex incr puts lsort range string
%

I think that lite standard scripting language (shell) may be useful for
yours aims too.

Happy scripting,

     	Sergei Gavrikov

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2006-06-02 14:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.63.0606021714120.27131@sg.belavox.gomel.by \
    --to=sg@belvok.com \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).