response
parent
5b2945cc92
commit
83826b39cf
|
@ -331,6 +331,8 @@ account all comments above (which doesn't mean it is above reproach :) ). --[[W
|
||||||
>>> it shouldn't (but I haven't verified that really happens).
|
>>> it shouldn't (but I haven't verified that really happens).
|
||||||
>>> That could certianly be a show-stopper. --[[Joey]]
|
>>> That could certianly be a show-stopper. --[[Joey]]
|
||||||
|
|
||||||
|
>>>> I think this can happen in the new closure based code. I don't think this could happen in the old code. -- [[Will]]
|
||||||
|
|
||||||
>>>> Even if that works, this is a good argument for having a syntactic difference between named pagespecs and normal pages.
|
>>>> Even if that works, this is a good argument for having a syntactic difference between named pagespecs and normal pages.
|
||||||
>>>> If you're joining two pagespecs with 'or', you don't want a named pagespec in the first part overriding a page name in the
|
>>>> If you're joining two pagespecs with 'or', you don't want a named pagespec in the first part overriding a page name in the
|
||||||
>>>> second part. Oh, and I assume 'or' has the right operator precedence that "a and b or c" is "(a and b) or c", and not "a and (b or c)" -- [[Will]]
|
>>>> second part. Oh, and I assume 'or' has the right operator precedence that "a and b or c" is "(a and b) or c", and not "a and (b or c)" -- [[Will]]
|
||||||
|
|
Loading…
Reference in New Issue