On Thu, 2005-03-03 at 14:40, murphy pope wrote:
> > murphy pope wrote:
> > >>The Named Node "Debacle"
> > >>---------------------------
> > >>
> > >>I wanted to be able to attach a "node name" attribute to each node,
> > >>and then be able to replace:
> > >>
> > >>STORE LISTEN ( ORIGIN = 1, RECEIVER = 2, PROVIDER = 3 );
> > >>
> > >> with, let's say:
> > >>
> > >>STORE LISTEN ( ORIGIN NODE = 'org master', RECEIVER NODE = 'data warehouse', PROVIDER NODE = 'whois server' );
> > >>
> > >>I'm sure you'll agree that the latter is much more mnemonic than
> > >>something involving perhaps-cryptic numbers :-).
> > >>
> > 
> > Why not just use shell variables instead? eg
> > 
> > ORG_MASTER=1
> > DATA_WAREHOUSE=2
> > WHOIS_DB=3
> > 
> > STORE LISTEN( ORIGIN=$ORG_MASTER, RECEIVER=$WAREHOUSE, PROVIDER=$WHOIS_DB );
> > 
> > They're only defined once, and are just as descriptive inside the slonik 
> > script file.
> 
> Shell variables don't work in a slonik script - they work in a shell
> script wrapped around a slonik script. 

I thought slonik scripts WERE shell scripts...?