Mercurial > urweb
comparison doc/manual.tex @ 661:d5552715db53
Update compiler phases
| author | Adam Chlipala <adamc@hcoop.net> |
|---|---|
| date | Thu, 12 Mar 2009 12:23:23 -0400 |
| parents | 9abeb533f6a7 |
| children | 039ad51cf9c3 |
comparison
equal
deleted
inserted
replaced
| 660:9abeb533f6a7 | 661:d5552715db53 |
|---|---|
| 1608 | 1608 |
| 1609 \subsection{Shake} | 1609 \subsection{Shake} |
| 1610 | 1610 |
| 1611 Remove all definitions not needed to run the page handlers that are visible in the signature of the last module listed in the \texttt{.urp} file. | 1611 Remove all definitions not needed to run the page handlers that are visible in the signature of the last module listed in the \texttt{.urp} file. |
| 1612 | 1612 |
| 1613 \subsection{Rpcify} | |
| 1614 | |
| 1615 Pieces of code are determined to be client-side, server-side, neither, or both, by figuring out which standard library functions might be needed to execute them. Calls to server-side functions (e.g., $\mt{query}$) within mixed client-server code are identified and replaced with explicit remote calls. Some mixed functions may be converted to continuation-passing style to facilitate this transformation. | |
| 1616 | |
| 1617 \subsection{Untangle, Shake} | |
| 1618 | |
| 1619 Repeat these simplifications. | |
| 1620 | |
| 1613 \subsection{\label{tag}Tag} | 1621 \subsection{\label{tag}Tag} |
| 1614 | 1622 |
| 1615 Assign a URL name to each link and form action. It is important that these links and actions are written as applications of named functions, because such names are used to generate URL patterns. A URL pattern has a name built from the full module path of the named function, followed by the function name, with all pieces separated by slashes. The path of a functor application is based on the name given to the result, rather than the path of the functor itself. | 1623 Assign a URL name to each link and form action. It is important that these links and actions are written as applications of named functions, because such names are used to generate URL patterns. A URL pattern has a name built from the full module path of the named function, followed by the function name, with all pieces separated by slashes. The path of a functor application is based on the name given to the result, rather than the path of the functor itself. |
| 1616 | 1624 |
| 1617 \subsection{Reduce} | 1625 \subsection{Reduce} |