On Mon, Dec 17, 2001 at 08:38:36AM -0700, Bryan Field-Elliot wrote: > My main point, Craig, is that it seems a bummer that we continue to > develop frameworks in Java which steer the developer further and further > away from the benefits of compile-time checking, and more and more > towards activities which take a String as a runtime parameter in order > to describe the intended behavior. My opinion is that there's a > messiness and error-proneness that it introduces, which wouldn't be > there with old-fashioned, fully compliation-time checked code. But > perhaps this isn't the place to discuss it, as everyone here has too > much vested in what's been built. > > Bryan > This is unavoidable whenever your system interfaces with other type systems - be it a user interface or a sql database or whatsoever. Servlet environment was not designed from the ground up and had to be interfaced to a working world. http parameters come in as strings database result sets com in as sql datatypes, etc.: you have to feed them and transform to java types. However, your application model cab fully enjoy the advances of compile time type checking.
incze -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
