re: why extra slash in regex? (was "Warning our Fellow Monks")

The line:

$siteinfo[1] =~ /^[^.]+/(\w+\.\w+)$/ or ...
[download]

in Ovid's example has me confused. The extra slash (/) in the middle is throwing me off. At first glance, it looks like he meant to use the s/// operator. At second glance, it becomes apparent that it's meant as a directory separator (to exclude things like "../../". However, doesn't placing a '/' in a regexp delimited by '/' characters require an escape character (\)?

(I must be getting a mild case of LTS)

Comment on re: why extra slash in regex? (was "Warning our Fellow Monks") Select or Download Code

Replies are listed 'Best First'.
(tye)Re: why extra slash in regex? (was "Warning our Fellow Monks") by tye (Sage) on Mar 17, 2001 at 00:45 UTC
Yes, you need to escape the / (with a \) or change the regex delimiter. - tye (but my friends call me "Tye")	[reply]
Re^2: why extra slash in regex? (was "Warning our Fellow Monks") by Anonymous Monk on Jul 25, 2005 at 14:35 UTC
`10 Print "I am not worthy" + CHR(10); 20 GOTO 10` [download] ---- Would be interested to see if the panel thought there's mileage in suggesting that it's unlikely that the user should want to open any type of file - and hence we could either assume an extension (and add it on explicitly before passing the filename to the ope() ?) - or offer a list, which would map to extensions (not just add on the field value (which could be faked to blank or a pipe)) Also - could the script not be forceably chrooted ? JAPHN (JAPH Novice)	[reply] [d/l]