<div dir="ltr"><div>The Toubleshooting and Tips FAQ for Web-server indicates that this is the case<br><a href="http://docs.racket-lang.org/web-server/faq.html">http://docs.racket-lang.org/web-server/faq.html</a><br><br></div> It explains how templates are compiled into the program, and then at the very end "If you insist on dynamicism, there is always <span class="">eval</span>."</div><div class="gmail_extra"><br><br><div class="gmail_quote"> On Wed, May 15, 2013 at 7:46 PM, Sam Tobin-Hochstadt <span dir="ltr"><<a href="mailto:samth@ccs.neu.edu" target="_blank">samth@ccs.neu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">On Wed, May 15, 2013 at 4:19 PM, Neil Van Dyke <<a href="mailto:neil@neilvandyke.org">neil@neilvandyke.org</a>> wrote:<br> ><br> > 1. You are using eval because you *necessarily* have arbitrary Racket code<br> > coming into your application from outside at run time? Or because the<br> > libraries you are using seem to want you to use "eval"? The former reason<br> > is legitimate, but rare. If the latter reason, there should be a better<br> > way. ("eval" is almost always a bad idea, except for when it's<br> > fundamentally necessary. Do not be misled by gesticulating CS 101<br> > lecturers; they are talking about theory.)<br> <br> </div>I think there are genuine uses for things like `eval` to support<br> reloading code/plugins/templates as well, which always at least<br> implicitly involves `eval`.<br> <span class="HOEnZb"><font color="#888888"><br> Sam<br> </font></span><div class="HOEnZb"><div class="h5">____________________<br> Racket Users list:<br> <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br> </div></div></blockquote></div><br></div>