Gerald Richter wrote: > > No it applies to the source! Otherwise Embperl is not able to create valid > Perl code out of it. >
Ok. I realize that this is an architectural/design decision, but my gut feeling is that it's counter-intuitive to the average programmer. Here's why: The Embperl model is fundamentally about dynamically creating HTML. This obviously means conditional code and loops. A programmer does not intuitively expect *conditional* HTML code to "count" in a syntactic sense before it is actually executed. For example, you may have several conditionals inside a loop, each of which contains some kind of HTML fragment. Each of these conditional fragments may contain repeated instances of the same HTML fragment, in a slightly different format. Any interesting (i.e. non-trivial) code will have this kind of thing. Why should each case of conditional HTML which contains (e.g.) a <UL> or </UL> tag be counted in the HTML syntax checking, even though it's not actually included in the final page? This kinda negates the whole convenience of having conditional code. I know that you can disable the Embperl syntax checking with the directive you specified, but this introduces additional overhead and potential for error (since you need to remember to turn it back on again after). Besides, it would surely be nice to be notified of errors in your HTML, *especially* in complex cases where you need to build some kind of nested lists by using loops and conditionals. Surely the checking of HTML syntax should be on the code which is actually generated, not on the source. Just my two cents, as I said before I realize it's an architectural decision, and might even be extremely hard to implement it this way. Not a huge deal but I thought it worth mentioning... All the best -Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
