> > Well it is getting double interpreted. First in the qr//
> then later in the
> > eval when that qr is strignified.
>
> Yeah, and that causes nasty errors. I don't think there should be
> double interpolation though.
I thinks its pretty well impossible to do what Damian is doing without
encountering this problem.
I havent thought about how difficult it is to work around.
> > End result, it never even got to backup_line to match the
> yellow against the
> > yellow!
>
> I think I've been looking at this for so long I'm actually
> seeing it any more.
That happens to me too.
> Well, it's producing the "right" error messages now. I think
> I'll just
> quietly leave it alone for a while and put a big warning in
> there not to
> touch it ;)
With a note like :"Caution: Here Be Dragons"
>
> > Uhuh. In fact, my tendency is to use {1} as the autoaction
> and to explicitly
> > provide the others. I find that usually matches my thinking better.
>
> Two thirds of my rules all have the same action:
> { $options{$where}{$item [1]} = $item [3]; }
> so it makes sense (to me at least) to use an autoaction.
I didnt say that it would match your thinking....
> > Once you stop wanting to murder me for the above comments
> please let me know
> > how it worked out.
>
> So far so good; it's parsing correctly, planning the backups
> correctly,
> now I need to add the report generation, write an accurate config file
> (I'll probably find a couple more bugs in my grammar), and start
> testing. Should be finished soon, says he foolishly.
Great. Glad to hear it worked out ok.
Yves
