From: Jan H. <hi...@wi...> - 2000-12-08 00:46:17
|
On Fri, Dec 08, 2000 at 12:47:33AM +0100, Arno Hollosi wrote: > > > Nested IF-blocks work already. The only thing you can't nest is twice > > > the same condition, i.e. ###IF:ADMIN### .... ###IF:ADMIN### > > > But I can't think of a case where such a construct is necessary. > > > > When you also introduce blocks for ###IF:COPY### and ##IF:LOCK## then the > > problem will appear. > > Why do I get the feeling that you didn't read the manual? ;) I only did a grep "IF:". That's what happens if you try to be clever. :-} > a) these if-blocks already exist > b) there is no problem mixing them (unless there is some bug), because > if you look at the corresponding endif it says ###ENDIF:COPY###, > ###ENDIF:LOCK### -- no problems with a simple straight-forward regexp. Hm. Now I see that you are matching the blocks seperately, once for COPY, once for LOCK and once for ADMIN. And that *does* work correctly unless you are nesting a COPY block inside a COPY block, but that would be nonsense anyway. So, yes, you are right, there will not be any problems with that. > I start to like this IF-less idea more and more. Maybe we should migrate? > I don't know - it's not such an urgent problem. Once people start really using it, it will be very hard to get it out again. By the way, what *are* the urgent problems? Is the list on sourceforge correct? -- Jan Hidders |