Alpheus Madsen:
This is actually a major reason I'm interested in Sweet-Expressions,
myself. I'd like to use some form of Common Lisp as a shell, and it
would be kindof awkward to have to use parentheses for everything.
If you want to write *scripts* using a Lisp-like language, scsh might be
Okay, I have sweet-expressions working as a shell scripting language. I did
this by modifying unsweeten so that a leading ;# and ;! are generated
without the semicolon.
To try it out, just install scsh (Scheme Shell). Here's a simple demo.sscm
file:
On Fri, Jul 27, 2012 at 11:43 AM, David A. Wheeler
dwhee...@dwheeler.com wrote:
I'd like to wrap up and have a release by around July 31.
We're mostly ready. We have a package that installs using autoconf, with
lots of useful stuff (sweet, unsweet, sweet-guile, neoteric-guile,
On 7/26/12, David A. Wheeler dwhee...@dwheeler.com wrote:
But now you can't use my-subst. You *could* replace it with
unsweeten.in and sweeten_header.in, and add to
AC_CONFIG_FILES([Makefile src/unsweeten src/sweeten_header]) or some
such - GUILE_PROGS automatically includes @GUILE@ in an
I have a (possibly controversial, possibly insanely stupid) feature
request:
So, curly infix is great because it's simple to understand, easy to
implement, and retains homoiconicity. However, it would be *really* nice to
be able to define infix operators that don't need to be surrounded by curly
Alan Manuel Gloria:
buNDlE BunDEl
Awesome, pushed.
And we have a new kind of error: If you use ! indents, and later
split a line, this won't work:
!hello( ...
!
!)
Because the ! on the middle and last line are *NOT* indent chars.
I'm really striving to make
Hi David:
On Fri, Jul 27, 2012 at 1:53 PM, David A. Wheeler dwhee...@dwheeler.comwrote:
I think that won't work at all, for same reasons that version 0.1 didn't
work out so well.
In version 0.1 of my readable approach, infix operators were
automatically detected. In that case, it used
