Le Tuesday 11 November 2008 21:47:55 Ian Hilt, vous avez écrit :Which is perfectly normal. The first \s* wanted spaces, it got them. But it left nothing for the capturing .+ behind. And any quantifier (except when it is possessive) _MUST_ backtrack in order for the full regex to complete. This is why the .+ captured the space: the first \s* was perfectly fine with no space at all, and the second, well, didn't find any space but it didn't care either. -- Francis Galiegue ONE2TEAM Ingénieur système Mob : +33 (0) 6 83 87 78 75 Tel : +33 (0) 1 78 94 55 52 fge@one2team.com 40 avenue Raymond Poincaré 75116 Paris -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Evgeniy Polyakov | Re: [BUG] New Kernel Bugs |
git: | |
| Gerrit Renker | [PATCH 28/37] dccp: Integration of dynamic feature activation - part 3 (client side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Tantilov, Emil S | WARNING: at include/net/sock.h:417 udp_lib_unhash |
