what's the difference between <% %> and <script language="vbscript" runat="server"> in classic asp?

Question

I couldn't find much documentation on the web

so far now, the obvious difference seems to be that you cant mix html and vbscript using the "script" tag

for example, this is ok

<% public sub display_literal() %>
  literal
<% end sub %>

but with the script tag you should

<script language="vbscript" runat="server">
public sub display_literal2()
    response.write "literal2</br>"
end sub
</script>

on this page

http://www.newobjects.com/pages/ndl/alp/asp-structure.htm

it says that

In classic ASP the script written in the default script language for the page (i.e. the language assumed for the <% %> tags) is executed second - e.g. all the script code in <% %> tags is initialized after all the <SCRIPT RUNAT=SERVER ...> scripts.

but I made a couple of tests and couldn't verify it...

I'm asking because I had a script (I don't have it at hand right now) that using <% %> gave me an error, changing it to the <script> tag solved the problem, but I'd like to know why....

anyway, I guess that we should use the <script> tag for functions and procedures that are to be called from <% %> tags... right?

Answer 1

First off you need to understand that there's a difference in the way server-side script tags are handled depending on whether the language specified is the same as the default language for the page.

The order is this:-

1. Run all scripts in <script runat="server" tags where the language specified does not match the default language. These are executed in document order.
2. Run the default script. That means perform the implied writes to the response where there is static content in the page (the stuff not in runat="server" tags or inside <% %>) and any intervening code in <% %> again in document order obviously.
3. Run any code at the global level found in <script runat="server" tags where the language matches the default script language.

Note that all script has an initial parse before executing phase 1, hence any functions that may be defined by scripts run in phase 3 will be available for calling from phase 1.