Skip to Content.
Sympa Menu

sm-sorcery - [SM-Sorcery]Language wars...

sm-sorcery AT lists.ibiblio.org

Subject: Discussion of Sorcery related topics

List archive

Chronological Thread  
  • From: Tony Smith <tony AT smee.org>
  • To: sm-sorcery AT lists.ibiblio.org
  • Subject: [SM-Sorcery]Language wars...
  • Date: Mon, 7 Oct 2002 14:40:53 +0100

All,

I wanted to pass on a suggestion for the future direction of sorcery on the
premise that if you don't speak up, you'll never be heard :-)

I know that we regularly endure the round of language wars and it seems that
Perl is under consideration for the future (2.0/3.0) but I have an idea which
would allow us to stay true to our roots and address some of the problems
with the current architecture.

What if the DETAILS file was not written in bash, but just a simple tag=value
format text file that could be easily grep'd or parsed? (Just the DETAILS
file, not the rest)

1. No need for sorcery to source every details file in a tree to find a spell:

find . -NAME DETAILS | xargs grep -l "SPELL=$SPELL"

would be an easy implementation of "gaze where". All commands that work on
sets of spells would benefit from this.

2. The CONFIGURE/BUILD etc. etc. scripts can still be bash so we get all the
benefits of having a build system based on the tools that you'd use to build
these packages interactively. [This is one area where I can see real
problems for a Perl/Python/Ruby/... implementation]

Thoughts?

Tony.






Archive powered by MHonArc 2.6.24.

Top of Page