From: mattmobile@proweb.co.uk
To: 9fans@9fans.net
Subject: [9fans] R G Loeliger meets Glenda
Date: Mon, 23 Feb 2009 19:23:47 -0500 [thread overview]
Message-ID: <a815e0a82e20219446b8d1b81f280dde@steponnopets.net> (raw)
My first stab at a TIL was in AVR assembler but it was more fun to write the code than to find a way to use it.
I still don't have a use but at least I don't have to run it on the AVR anymore to experiment
first an example run
cpu% /n/sources/contrib/maht/rc/til
abc¯def
123
emit
abc def
123
: emit4 emit emit emit emit
1 2 3 emit4
321
1
swp 3 2 swp dup dup drop emit4 emit
3321
As you may see
gets converted to newlines and ¯ (alt__ in plan9, alt0175 on the numpad in windows drawterm) gets converted to a space (any better ideas?)
It's the fruit of an evening's playing, so I've got a few features to add yet (saving the words will be trivial as you should see from the code)
I should give props to BashForth for giving me the idea, but I've not looked at any of it's code (ugh).
matt
reply other threads:[~2009-02-24 0:23 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=a815e0a82e20219446b8d1b81f280dde@steponnopets.net \
--to=mattmobile@proweb.co.uk \
--cc=9fans@9fans.net \
/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).