comment on

Just to add to what the other monks have said on the subject, this is from the CGI.pm docs:

There will be some times when you want to produce the start and end tags yourself. In this case, you can use the form start_tag_name and end_tag_name, as in:

print start_h1,'Level 1 Header',end_h1;

With a few exceptions (described below), start_tag_name and end_tag_name functions are not generated automatically when you use CGI. However, you can specify the tags you want to generate start/end functions for by putting an asterisk in front of their name, or, alternatively, requesting either "start_tag_name" or "end_tag_name" in the import list. Example:

use CGI qw/:standard *table start_ul/;

In this example, the following functions are generated in addition to the standard ones:

start_table() (generates a <TABLE> tag)
end_table() (generates a </TABLE> tag)
start_ul() (generates a <UL> tag)
end_ul() (generates a </UL> tag)
[download]

I haven't tested it with every HTML tag, mind... ;-)

Update: here's a link to the relevant part of the CGI.pm docs (as suggested by PodMaster).

In reply to Re: Re: Re: CGI.pm Disillusionment by mooseboy
in thread CGI.pm Disillusionment by Cody Pendant

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks