[ruby-talk:00768] Ugly behavior using /<r1>/ .. /<r2>/ construct.

Hi,

I have some question/remarks...

Is there any difference between these two:

	(1) if /^start/ .. /^stop/; p "GOTCHA"; end
	(2) if /^start/ ... /^stop/; p "GOTCHA"; end

There seems no difference! But `...' should behave a little bit
different than `..', shouldn't it?

I would assume, that the then case would not entered for a line that
matches `/stop/' using `...'.

Furthermore the subpattern capturing doesn't work well. Please consider
following code:

	if /^title(\s+(.*))?/ .. /^end/
	   print "title=#$2\n";
	end

Here the variable `$2' will *never* have any other value than `nil'. I
assume, that this is because `$_' will be matched against both regexps.
As the second regexp doesn't match the first time the first one match,
`$2' will be reset to `nil'.

My proposal would be, that in such `..' construct, the variables `$n'
should only be set to the captured subpattern of the *matched* regexp.
The one that *doesn't* match, should not reset them! Only if both
doesn't match, they should be reset to `nil'.

What do you think?

\cle