From: Günther Thomsen on
On Jun 12, 11:12 am, Tim Bradshaw <t...(a)tfeb.org> wrote:
> Over the last couple of days, I've been gathering information from a
> number of machines about the number, types, and speeds of processors
> they have

I find myself often in similar situations (albeit without the
drama ;-)

> And, like it or not, Perl is the king, queen and crown prince of this
> kind of grovelling in the mud.
It's but one of many tools. For controlling other programs I have yet
to find something easier than 'expect' (if one can bear TCL). Perl's
open2() gets the job done, but not nearly as elegantly or simply.
Python's popen2() and the more recent subprocess module seem to fill
the same niche. How would I do this in (SB)CL / CLISP or racket?

> You could do it in Lisp, but why would you?
Personal preference mainly, a sense of aesthetics. Proper exceptions
and restarts would be nice too.
From: Michael J. Barillier on
>>>>> "dw" == Dan Weinreb <dlw(a)alum.mit.edu> writes:

dw> I've wondered sometimes about having a DSL within Lisp that
dw> would be good at the things that Perl is most used for, such as
dw> what you're talking about.

Me too. On my list of things to do is an implementation of a good chunk
of scsh <http://www.scsh.net/> in CL. Seems I'm frequently in Lisp when
I need to do some operation that's trivial in Perl or a shell script
(find/grep files, process/merge output, network I/O, etc), and having to
bust out of Lisp breaks flow. Might just have to set up a project this
weekend in my free time ... once I find it.

--
Michael J. Barillier /// http://www.blackwolfinfosys.net/~blackwolf/
_O_| "... Ideas are bulletproof."
__O| -- V
OOO|
From: Rob Warnock on
Michael J. Barillier <blackwolf(a)blackwolfinfosys.net> wrote:
+---------------
| >>>>> "dw" == Dan Weinreb <dlw(a)alum.mit.edu> writes:
| dw> I've wondered sometimes about having a DSL within Lisp that
| dw> would be good at the things that Perl is most used for, such as
| dw> what you're talking about.
|
| Me too. On my list of things to do is an implementation of a good chunk
| of scsh <http://www.scsh.net/> in CL.
+---------------

This is reasonable [I've played with trivial subsets of it], though
you do have to make some modifications of the SCSH syntax -- mainly
adding explicit backquotes in many places that SCSH doesn't require
them -- due to the facts that: (1) only the result of EVAL-ing backquoted
expressions is defined in the CL standard, *not* the results of READ-ing
them per se; and (2) READ-ing "naked" [unmatched] commas and ",@" tokens
are *NOT* permitted in the ANSI CL reader nor is the result defined,
whereas they *are* permitted and the result *is* defined for the Scheme
reader, and SCSH makes much use of that.

For more information on this issue, see my previous posts by searching for:

scsh common-lisp backquote group:comp.lang.lisp author:rob author:warnock

e.g.:

Subject: comma ("unquote") question
Message-ID: <BcSdnR4_J-YIh9KiXTWc-w(a)speakeasy.net>
http://groups.google.com/group/comp.lang.lisp/msg/00545caa0de7bf0b

Subject: Re: Which ones come first? - Macro question -
Message-ID: <F_ydnREZ5s5OqyDVnZ2dnUVZ_rmdnZ2d(a)speakeasy.net>
http://groups.google.com/group/comp.lang.lisp/msg/240679b0e7244bf6

Subject: Re: output of READ or rather, input to EVAL
Message-ID: <2fGdnShLTLjP_8jWnZ2dnUVZ_vOdnZ2d(a)speakeasy.net>
http://groups.google.com/group/comp.lang.lisp/msg/81c85ceb104b900b

Subject: Re: Dynamic unquote ( , )?
Message-ID: <9IudnYhzzoF6L2zeRVn-pA(a)speakeasy.net>
http://groups.google.com/group/comp.lang.lisp/msg/4a5fdca45a429603

and a few others... ;-}


-Rob

-----
Rob Warnock <rpw3(a)rpw3.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607

From: Michael J. Barillier on
>>>>> "rw" == Rob Warnock <rpw3(a)rpw3.org> writes:

rw> For more information on this issue, see my previous posts by
rw> searching for:

[snip]

Thanks, Rob. Definitely will check those posts. Sounds like ugly
backquote hackery is in store ...

--
Michael J. Barillier /// http://www.blackwolfinfosys.net/~blackwolf/
_O_| "... Ideas are bulletproof."
__O| -- V
OOO|