comment on

Hmm... instead of using <> to run through the files, you could do something like:
```
foreach my $in_fname (@ARGV) {
  ...
}
[download]
```

As for a regex, you could do:

  $input_txt =~ s/\<script.*?\<\/script\>//igs; # remove code
  $input_txt =~ s/\<.*?\>//gs; # remove html tags
  $input_txt =~ s/\&nbsp;/ /gs; # &nbsp -> space
  $input_txt =~ s/\s{2,}/ /gs; # Remove extra spaces
  print $input_txt;
[download]

It's not valid HTML to have <> elements inside of other HTML tags (they should be entity-encoded as in:

  <a href="" onClick="alert('&lt; foo! &gt;');">
  not:
  <a href="" onClick="alert('< foo! >');"> Invalid HTML!
[download]

However, if they're there, then you can do the regex inside a while loop:

  while( $input_txt =~ s/\<.*?\>//gs ) {};
[download]

Using modules is probably better. Every time you reinvent the wheel, somewhere, a monk sheds a tear...

In reply to Re: Simplify parsing a file by saintly
in thread Simplify parsing a file by Anonymous Monk

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.