On Tue, 10 Aug 1999, Peter wrote:
[ ... ]
> So when people like yours truly complaint on how complicated they
> are to use, then came forth those derogatory remarks such as
> "unreformed perl programmer", "messy coder" etc-etc ....... well go
> ahead and make yourself feel superior by trashing out at us .......
[ ... ]
It's true some people made some, er, unhelpful remarks, but several
responded with reasons why perl's here-document (which originated in
shell programming, BTW) was not really appropriate for Java, either
syntactically or design-wise (i.e. in an object-oriented sense). I'm
sure it is possible to code up something like it that would fit with
Java, but it is really just syntactic sugar that is probably more
appropriate as an editor macro than a Java language construct.
Really, as some people have said, worrying about being able to use
Perl's here-document vs. a bunch of out.println()'s in Java is not a
deep issue. It has more to do with the different nature/purposes of
the languages than how difficult they are to use. And as far as I can
recall, that was the only thing you complained about and/or the only
suggested improvement you made. You didn't really say more about what
about those template systems/JSP is so problematic, and/or what a
better solution would consist of.
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html