I'm afraid I take issue with several of your points:
Java, on the other hand, is a completely different type of programming language, in that it's object-orientated. That doesn't mean that Perl and Java couldn't solve a given problem, but it just means that there are some things Java could do better than Perl, and vice versa.
A) I don't think you can call any language 'object oriented'. OO is a design style, not a function of the language. You can write OO code in C and write procedural code in java. Granted in general it's much easier to write OO in java and procedural in C, but it doesn't make C a 'procedural language' or java an OO language.
B) Perl has just as many OO'ish features as java does, you could write every single thing as a class if you wanted to. (Well, except for a line that looked like package main; new module;
C) If you really wanted to find the differences you should note that java is a much lower level/stricter programming language, meaning that you have to manually deal with datatypes such as int or char, and once you declare something an int it stays an int and so on. (lets not get in to scalar datatypes, or object inheritance issues). Java has a number of other differences but I find that to be the most important one.
ASP, atleast in my somewhat limited understanding, is a frame work for CGI type applications that allows a number of different languages access to a number of basic methods and data, such as form data and session handling (I think). It also lets these different languages work together much closer then without it, passing datastructures back and forth and so on (Again, I think).
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.