Pascal Bourguignon <···@informatimago.com> wrote:
+---------------
| With some time, we could also implement in common lisp the facilities
| of scsh (scheme shell).
+---------------
Yes, well, *almost*... See my several postings on why limitations
in CL's backquote makes it impossible[1] to *exactly* copy Scsh's
syntax, athough one can come quite close.[2]
-Rob
[1] Unless one replaces the default CL backquote readmacro, that is.
[2] That is, instead of the following, which is legal Scsh
["run" is a macro which performs "implicit quasiquoting"]:
(run (ls ,@flags ,dir))
to make it legal CL one might have to type this:
(run `(ls ,@flags ,dir))
-----
Rob Warnock <····@rpw3.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607
····@rpw3.org (Rob Warnock) writes:
> Pascal Bourguignon <···@informatimago.com> wrote:
> +---------------
> | With some time, we could also implement in common lisp the facilities
> | of scsh (scheme shell).
> +---------------
>
> Yes, well, *almost*... See my several postings on why limitations
> in CL's backquote makes it impossible[1] to *exactly* copy Scsh's
> syntax, athough one can come quite close.[2]
>
>
> -Rob
>
> [1] Unless one replaces the default CL backquote readmacro, that is.
>
> [2] That is, instead of the following, which is legal Scsh
> ["run" is a macro which performs "implicit quasiquoting"]:
>
> (run (ls ,@flags ,dir))
>
> to make it legal CL one might have to type this:
>
> (run `(ls ,@flags ,dir))
Well, yes, for interactive use, at the REPL, I wouldn't mind a special readtable.
There are already some special syntaxes, for example for debugger/toplevel commands.
--
__Pascal Bourguignon__
On Mar 31, 4:10 pm, Neil Baylis <···········@gmail.com> wrote:
> Twice today, I found myself typing:
>
> (ls -al)
>
> at the bash prompt.
>
> sigh,
>
> Neil
My job is programming in C. There have been several times now where I
start typing a line of code and then get a kinda lost feeling about
the parentheses... and I start trying to do stuff like this:
(printf "PID is %d\n", (getpid));
As you can see, it's a kind of unholy union between C (note the
semicolon and comma) and Lisp. When I type this, I realize it's time
to take a break :)
John
On Apr 1, 5:53 pm, John <··········@gmail.com> wrote:
> On Mar 31, 4:10 pm, Neil Baylis <···········@gmail.com> wrote:
>
> > Twice today, I found myself typing:
>
> > (ls -al)
>
> > at the bash prompt.
>
> > sigh,
>
> > Neil
>
> My job is programming in C. There have been several times now where I
> start typing a line of code and then get a kinda lost feeling about
> the parentheses... and I start trying to do stuff like this:
> (printf "PID is %d\n", (getpid));
> As you can see, it's a kind of unholy union between C (note the
> semicolon and comma) and Lisp. When I type this, I realize it's time
> to take a break :)
>
Not to forget all those times one forgets the trailing semicolons
(after too much time hacking bash scripts or Python apps) when back in
real life(tm) at work w/ C++. *sigh*
--
Mikael Jansson
http://mikael.jansson.be/
On Mar 31, 7:10 pm, Neil Baylis <···········@gmail.com> wrote:
> Twice today, I found myself typing:
>
> (ls -al)
>
> at the bash prompt.
>
> sigh,
>
> Neil
I think I top you:
This morning I woke up dreaming a little snippet in lisp (using loop
to implement the Goertzel algorithm to calculate the Fourier component
at one particular frequency) I can think of so many much more fun
dreams :-(
Mirko