Mudlet

selectCaptureGroup() should start indexing at 1

Bug #298235 reported by Vadim Peretokin
2
Affects Status Importance Assigned to Milestone
Mudlet
Fix Released
Low
Unassigned
Mudlet beta

Bug Description

selectCaptureGroup() should start it's indexing at 1, instead of 0 as it is currently - it is standard in regex wildcard that 0 implies the whole match, and 1 is the first matched wildcard.

See original description
Revision history for this message
Vadim Peretokin (vperetokin) wrote :

This is with mudlet 13112008

Changed in mudlet:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Heiko (koehnheiko) wrote :

RTFM - 1st group is group 0 not group 1

Changed in mudlet:
status: Confirmed → Invalid
Revision history for this message
Vadim Peretokin (vperetokin) wrote : Re: [Bug 298235] Re: selectCaptureGroup() doesn't work properly

This is still an issue because in standard regex, group 0 means the whole
match. Hence this thing needs to start counting from 1 like everyone else
does.

Revision history for this message
Vadim Peretokin (vperetokin) wrote : Re: selectCaptureGroup() doesn't work properly

Even with the (buggy) behavior of starting the index at 0, the trigger exhibits the same behavior: http://www.ubuntu-pics.de/bild/5672/screenshot_37_qnu72r.png

Vadim Peretokin (vperetokin)
description: updated
Changed in mudlet:
importance: High → Low
status: Invalid → Confirmed
Vadim Peretokin (vperetokin)
Changed in mudlet:
milestone: none → beta
Heiko (koehnheiko)
Changed in mudlet:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.