How about more descriptive names for easier searching on the following nodes? My suggestions are much longer, but they contain enough information to guess at the content of the nodes (unlike the original names).

• arrays (okay)
• CGI programming
  • Rename this may be basic CGI and carriage returns to How do I handle mid-line carriage returns in a flatfile database?
  • Rename File Upload to Can I handle file uploads with Perl without using a module like CGI.pm?
  • Rename Spaces in paramater (sic) to When constructing a URL from script variables, how do I make sure that spaces are properly handled?
  • Rename Validating form fields to How do I detect and handle empty form fields?, and combine it with its cousin Validating Form fields (take two)
  • Rename Managing user sessions to How do I maintain the security of user session information? This could easily be combined with a related question, Protecting login information passed thru URLs
  • Rename How I can maintain a session cookie to How do I set a cookie to expire when the user closes all browser windows?; maybe expand the question and answer to address how to handle cookie expiration more generally
• data formatting
  • This whole section is filled with q&a that belongs in SOPW or another Q&A section, mostly strings and regexs. Is this section about data formatting the concept or about the reserved word format used in templating?
• database programming
  • move Confusing SQL Query and Query not executing properly to SOPW because they aren't likely to be frequently asked, at least not in their existing forms
  • do something with Problems installing DBI module for PERL; it contains a useful tidbit about 5.6 that I'd hate to see lost, but the question is so generally phrased as to be basically useless.
• dates and times
  • Rename time() smaller than seconds? to something like Is there a way to call time() with an increment smaller than seconds?

Well, that's the first five sections. *yawn* I'll come back to it later.

e-mail neshura

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

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

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