On 8 March 2014 08:47, Saku Ytti wrote:
> On (2014-03-07 19:44 +), Pedro Cavaca wrote:
>
> > Why wouldn't ".{3}" work, for this case?
>
> Because the OP wants a same atom N times, not any atom N times.
>
Of course, what was I thinking? I'll crawl back to my hole now... Thanks
for being gentl
On (2014-03-07 19:44 +), Pedro Cavaca wrote:
> Why wouldn't ".{3}" work, for this case?
Because the OP wants a same atom N times, not any atom N times.
--
++ytti
Hi,
thanks for all info but with my 11.4R7.5 I cannot implement the check.
Regards,
Marco
2014-03-07 20:47 GMT+01:00 Pedro Cavaca :
>
>
>
> On 7 March 2014 19:44, Pedro Cavaca wrote:
>
>>
>>
>>
>> On 7 March 2014 19:26, Michael Loftis wrote:
>>
>>>
>>> http://www.juniper.net/techpubs/en_US/j
On 7 March 2014 19:44, Pedro Cavaca wrote:
>
>
>
> On 7 March 2014 19:26, Michael Loftis wrote:
>
>>
>> http://www.juniper.net/techpubs/en_US/junos13.3/topics/usage-guidelines/policy-configuring-as-path-regular-expressions-to-use-as-routing-policy-match-conditions.html
>>
>> There's no backref s
On 7 March 2014 19:26, Michael Loftis wrote:
>
> http://www.juniper.net/techpubs/en_US/junos13.3/topics/usage-guidelines/policy-configuring-as-path-regular-expressions-to-use-as-routing-policy-match-conditions.html
>
> There's no backref support in the regex subset that juniper has chosen
> to im
http://www.juniper.net/techpubs/en_US/junos13.3/topics/usage-guidelines/policy-configuring-as-path-regular-expressions-to-use-as-routing-policy-match-conditions.html
There's no backref support in the regex subset that juniper has chosen
to implement, see
http://juniper.cluepon.net/index.php/ER_Det
6 matches
Mail list logo