I think you're both talking past each other here. What I believe he's trying to emphasize may be that while with perl you've got this:
#!/usr/bin/perl print "Hello, world\n";
In Java you're going to have to break out:
public class HelloWorld { public static void main( String args[] ) { System.out.println( "Hello, world\n" ); } }
Perl makes it dead simple to whip out call-this-call-this-call-this-boom-done style code, whereas to get the same thing in Java you've got to write a whole lot more overhead explicitly (i.e. you'd have a whole lot of static methods in some class rather than just a couple of subs hiding at the bottom of your quick, declarative Perl).
Update: Upon reflection, that's probably not what they mean by OO only. Maybe someone's thinking "pure OO", but then Java's not (c.f. int and other primitive, non-object types). Never mind me.
But maybe my last paragraph will be of some use to the OP.
Or not. Meh.
In reply to Re^5: A Perl vs. Java fight brews
by Fletch
in thread A Perl vs. Java fight brews
by Moron
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |