comment on

Hi all,

I am adventuring in the world of perl and web based applications, and I stumbled upon a very important matter regarding which way HTML (or your output of choice) is to be printed: via inline PRINT (something with vars... ENDHTML is surely better) or via TEMPLATE reading, parsing and outputting?

ENDHTML example

$myvar= 'foo';
print <<ENDHTML;
<html>
<body>
Todays variable is: $myvar
</body>
</html>
ENDHTML
[download]

TEMPLATE SPAGHETTI example

open $templatefile;
$newfilecontent= &parse($templatefile, \@replacements);
open $newfile;
print ($newfile, $newfilecontent);
[download]

I've come to the conclusion ENDHTML printing is more CODE-WISE and maybe more practical to develop, but its surely not open to flexibility. On the other hand, the convenience of template parsing means lots of code for managing errors and exceptions...
Which are your personal ideas on the most PRACTICAL way to proceed?

Thanks in advance

In reply to OUTPUT: inline or template_based? by CodeHound

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks