I chose that because such an approach is commonly used in several
server-side scripting languages, such as ASP, PHP, etc. PHP uses "<?php ...
?>" instead of "<% ... %>". The point I am trying to make is to use SOME
kind of unique identifiers should be used to denote where special processing
should start and stop. Which tokens are actually decided on is jbk's
Yes, there is, and it is clearly stated as such in the Win32 API
documentation for ExpandEnvironmentStrings():
"The size of the lpSrc and lpDst buffers is limited to 32K."
Not exactly. From a theoritical standpoint, you are correct that line
breaks should not make any difference. In real world use, however, you have
to be careful with them because line breaks DO make a difference in certain
situations. Depending on what the surrounding HTML content is, line breaks
can actually introduce extra spacing in the browser display, amongst other
possible minor/subtle side effects. That may or may not be
desirable/acceptable to the user.
It may help the parser some, but in actuality the more inline the processing
tags are allowed to be, the more flexible the parser will be overall.