Re: [Bashburn-info] Substantial change to the configure function.
Brought to you by:
bashburn
|
From: Nick W. <ni...@uk...> - 2008-09-03 06:52:29
|
On Wed, 3 Sep 2008 07:26:10 +0100
Nick Warne <ni...@uk...> wrote:
> On Wed, 3 Sep 2008 01:00:17 -0400 (EDT)
> "Steven W. Orr" <st...@sy...> wrote:
>
> > We now have a Revert function in the Configure option.
> >
> > If you change a value, it will not take place until you Apply it. If
> > you Revert, then all changes will be wiped out.
> >
> > This is a rather substantial change and I (as usual) think I got it
> > right. No bets.
> >
> > There is some English language text in configure.
> >
> > And finally, the BashBurn.sh had to get re-structured. It's vital
> > that all sourcing not happen from the context of a subroutine. To
> > make a long story short:
> >
> > -------bar.sh------
> >
> > typeset -ri intval=44
> >
> > ------end of bar.sh
> >
> > foo()
> > {
> > . bar.sh
> > }
> >
> > will cause intval to be a local variable inside foo and never
> > globally available. You might not care except that I still want the
> > option of creating and declaring global variables.
> >
> > Enjoy. It's 1AM and I'm outtahee.
> >
>
> OK, I get syntax errors when starting... it looks like bash doesn't
> like empty functions. If I remove them, all seems well but I don't
> know what you was doing here so haven't changed anything.
>
> line 285: syntax error near unexpected token `}'
>
> source_language_modules()
> {
> } <---------------------------------
>
I get around the above error by adding a 'continue'.
Another thing is 'apply changes' doesn't work.
Nick
--
Free Software Foundation Associate Member 5508
|