Re: Re: How many bugs can *you* find

Replies are listed 'Best First'.
Re: Re: Re: How many bugs can you find by satchboost (Scribe) on May 01, 2001 at 02:13 UTC
To nitpick further, `[\n\r]` will replace every instance of \n or \r with a <p>. That means that, on Win32, you'll get two <p> and only one on Unix.	[reply] [d/l]
Re: Re: Re: Re: How many bugs can you find by MeowChow (Vicar) on May 02, 2001 at 02:31 UTC
To put an end to the picking of nits, you will not get two `<p>`'s under Win32 because the file has not been opened `binmode`. This means the OS will strip the `\r` line terminators for you. Also, the correct order for matching in `binmode` is `\r\n`, not the other way around. MeowChow s aamecha.s a..a\u$&owag.print	[reply] [d/l] [select]
Re: Re: Re: Re: How many bugs can you find by Beatnik (Parson) on May 01, 2001 at 23:53 UTC
To nitpick further doing `s///`'ing `\n` and `\r` separatly is faster using a char class. Greetz Beatnik ... Quidquid perl dictum sit, altum viditur.	[reply] [d/l] [select]
Re: Re: Re: Re: Re: How many bugs can you find by satchboost (Scribe) on May 01, 2001 at 23:58 UTC
That may be true in general, but the idea is to take the CRLF sequence in Unix (\n) and the CRLF sequence in Windows (\n\r) and replace either of them with <p>. To do that, one regex is simpler than two.	[reply]
Re (tilly) 6: How many bugs can you find by tilly (Archbishop) on May 03, 2001 at 05:53 UTC
Re: Re: Re: Re: Re: Re: How many bugs can you find by Beatnik (Parson) on May 02, 2001 at 00:02 UTC
Re: Re: Re: Re: Re: Re: Re: How many bugs can you find by satchboost (Scribe) on May 02, 2001 at 00:05 UTC


Welcome to the Monastery
	PerlMonks