Re: [Bashburn-info] Time to stabilize

[Steven W. O. <st...@sy...>]

On Monday, Sep 29th 2008 at 21:30 -0000, quoth Anders Lind?n:

=>It seems like things are calming down now, the interface and functions
=>seem to be stable. Things I suggest we do:
=>
=>* Serious testing of all functionality.
=>(I suggest changing the CD recording command to 'cdrecord -dummy' and
=>the DVD burning command to 'growisofs -dry-run' to not waste CDs/DVDs)
=>* Make sure translations are complete.
=>(No further changes that needs .lang-files updated will be accepted)
=>* Make sure documentation is updated.
=>
=>When these steps are done, merge trunk into 3.0 and release it. 
=>Do you all agree? Is there anything else you like to add? 
=>
=>Some restructuring like Steven has suggested and the gettextification
=>(And other things anyone can think of) should go into 3.1. 

Anders, that sounds good to me.

Just so you understand, I just made a change, yet again. I had created a 
function in BB.sh called source_non_language_modules. I eliminated that 
whole function in favor of just putting that code inline. I believe the 
problem we had today was related to the fact that that function had caused 
all the typedefs to become local variables inside 
source_non_language_modules, instead of being the globals we wanted them 
to be.

We really should be ok now.

As for testing, if possible, we need to beat on audiofunc. There really is 
some hairy code there and I'm concerned that no one noticed that it was 
broken before.

I'm actually building up a collection of tricks in bash that I had never 
developed before. In particular, there's an interesting concept that turns 
out to be useful, not from an algorithm perspective, but more from a 
patterns view. It goes something like this:

funcA()
{
    typeset stbe="$1"		# Something To Be Eval'd.

    while something_is_true
    do
	var=something
	eval $stbe
    done
}

But note that stbe might refer to var. Then we call funcA


xxx='I love a parade. Especially on a $var' # Notice the single quotes.
funcA "$xxx"

Note that xxx is just an uninterpolated string, and no one outside of 
funcA knows anything about var. This is used *all* over the place.

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net